Replicar en PC de laboratorio un Virtual Center, con Vmware Player

1-Configuración de Red, deshabilitar DHCP vmware player para que no choque con nuestra futura configuración de Red:
1. Click Start, then choose Settings>Control Panel.
2. Click Administrative Tools.
3. Double-click Services.
4. Scroll down and select VMware DHCP Service.
5. Right-click the highlighted line and choose Properties.
6. Click the Stop button.
7. In the Startup type list, select Disable or Manual.
8. Click OK.


Configuraciones de red que me han funcionado:
-Clientes y servidor poner en setting de red custom y vmnet8 (Nat)Server:


Para secularizar el arranque hacer estos pasos:

Integrating another (3rd party) boot menu for WDS in Windows Server 2008 R2 has changed compared with standard Windows Server 2008... here is how to do it...
  1. Download and extract syslinux-3.85.zip or later from http://www.kernel.org/pub/linux/utils/boot/syslinux  (it contains pxelinux)
  2. Copy the com32\menu\vesamenu.c32 and com32\modules\chain.c32 files to your WDS Server, to both the D:\RemoteInstall\Boot\x64 andD:\RemoteInstall\Boot\x86 folders.
  3. Copy the core\pxelinux.0 file to your WDS Server, to both the D:\RemoteInstall\Boot\x64 and D:\RemoteInstall\Boot\x86 folders, then rename it to pxelinux.com
  4. Download a nice background image (http://www.deployvista.com/Portals/0/DeploymentBackground.png), and save it in D:\RemoteInstall\Boot\x64 and D:\RemoteInstall\Boot\x86   
  5. In the D:\RemoteInstall\Boot\x64 and D:\RemoteInstall\Boot\x86 folders, make a copy of pxeboot.n12 and rename it to pxeboot.0
  6. In the D:\RemoteInstall\Boot\x64 and D:\RemoteInstall\Boot\x86 folders, make a copy of abortpxe.com and rename it to abortpxe.0
  7. Configure WDS to use the pxelinux.com boot file, in Windows Server 2008 R2 you have to do it through WDSUTIL, here are the commands:
  8. WDSUTIL /Set-Server /BootProgram:boot\x86\pxelinux.com /Architecture:x86
  9. WDSUTIL /Set-Server /N12BootProgram:boot\x86\pxelinux.com /Architecture:x86
  10. WDSUTIL /Set-Server /BootProgram:boot\x64\pxelinux.com /Architecture:x64
  11. WDSUTIL /Set-Server /N12BootProgram:boot\x64\pxelinux.com /Architecture:x64
  12. In the D:\RemoteInstall\Boot\x64 and D:\RemoteInstall\Boot\x86 folders, create a subfolder called pxelinux.cfg
  13. In the D:\RemoteInstall\Boot\x64\pxelinux.cfg and D:\RemoteInstall\Boot\x86\pxelinux.cfg folders, create a file named default with the following settings


DEFAULT   vesamenu.c32
PROMPT    0
NOESCAPE 0
ALLOWOPTIONS 0
# Timeout in units of 1/10 s
#TIMEOUT 300
MENU WIDTH 40
MENU MARGIN 0
MENU ROWS 12
MENU TIMEOUTROW 14
MENU HSHIFT 5
MENU VSHIFT 2
MENU COLOR BORDER 30;44    #00000000 #00000000 none
MENU COLOR TABMSG 1;36;44 #00000000 #00000000 none
MENU COLOR TITLE 1;36;44 #00000000 #00000000 none
MENU COLOR SEL   30;47    #40000000 #20ffffff
MENU BACKGROUND DeploymentBackground.png
MENU TITLE PXE Boot menu
MENU WIDTH 80
MENU MARGIN 18
MENU ROWS 4
LABEL wds
MENU PASSWD berrozi48900
MENU    LABEL Servicios de implementacion de Windows
KERNEL pxeboot.0
LABEL local
MENU    DEFAULT
MENU LABEL Arranque desde disco duro local
LOCALBOOT 0
LABEL Abort
MENU LABEL Cancelar PXE
KERNEL abortpxe.0

Here is how it looks...

Comentarios

Entradas populares de este blog

Orange Pi IoT 2G Flashear memoria NAND

Usar datos gratis para proyectos IoT FreedomPop y Orange Pi 2G IoT (también Simyo).

Configurar modem GSM en la Orange Pi 2G IoT (Orange España)