Implementering Ghost Cast Server - WDS. NIC driver problem

[Roudi]

Hei!

Må dessverre starte mitt første innlegg her, med et problem. Bedriften min har over lengre tid brukt Ghost Cast Server til å tanke maskinparken. Vi har begynt å se oss lei av å ha med oss cd plater rundt for og få bootet opp Ghost på klient maskinene. Så vi har nå tatt steget og installert WDS.

 

Fulgte Symantec Sin guide

og fikk i gang det hele. Vi har nå tatt i bruk noen nyere modeller av blant annet Dell D5400.

I guiden til Symantec står det at man må legge NIC driveren inn i mount\windows mappa.

Har testet dette, men det ser ikke lyst ut. Starter opp Ghost og når jeg prøver å koble til Ghost cast session, står den bare og søker evig. For meg virker dette som om den mangler driveren.

 

Er det noen som har noen råd/opplevd dette?

Vil legge til at jeg legger .sys filen inn på mount\windows

 

Mvh Rune

[Gjest Slettet-t8fn5F]

For å legge til nic-drivere til et boot-image på en WDS-server, bruker jeg denne oppskriften.

 

# Note The following procedure assumes that the Windows Automated Installation Kit (AIK) is installed on the WDS server. If the Windows AIK is not installed on the WDS server, you can perform the same procedure on another computer that does have the Windows AIK installed. Then, map a network drive to the WDS server.

 

1. On the WDS server, click Start, click Run, type wdsmgmt.msc, and then press OK.

2. Under your WDS server, double-click Boot images.

3. Right-click the boot image that you want, and then click Disable.

4. Right-click the same boot image, click Properties, and then click General.

5. Note the name and location of the boot image that is displayed in the File name box.

6. At a command prompt, type the following:

C:\program files\windows aik\tools\petools\copype.cmd x86 c:\windowspe-x86

Note Keep this command prompt window open for the next step.

Imagex /info Drive:\remoteinstall\boot\x86\images\boot.wim

Notes

* Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed.

* Boot.wim is the name of the boot image.

7. Note the boot index number of the bootable image that is displayed. To identify the boot index number, locate the line that contains "boot index: X."

 

Note X is the boot index number. The number indicates that image number X is marked as bootable and that the image is to be updated. The second image is the default image that you would typically modify. However, always verify which image is marked as bootable.

8. At a command prompt, type the following:

Imagex /mountrw Drive:\remoteinstall\boot\x86\images\boot.wim 2 mount

peimg /inf=driver.inf mount\Windows

imagex /unmount /commit mount

Notes

* Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed.

* Driver.inf is the name of the third-party driver.

* The Imagex /mountrw command mounts the specified image, with read/write permissions, to the specified directory.

 

# Enable the boot image on the WDS server. To do this, follow these steps:

 

1. On the WDS server, click Start, click Run, type wdsmgmt.msc, and then click OK.

2. Under WDS server, double-click Boot images.

3. Right-click the boot image that you want, and then click Enable.

 

Måtte bare ta alt med i tilfelle der skulle være noen spørsmål.

 

PS. Mener det blir feil at Symantec skal fortelle deg hvordan WDS skal brukes. Grunne til jeg synes det er feil, er at Symantec har en konkurerende tjeneste...

Hvorfor ikke bare bruke Microsoft sin WDS-server på den måten Microsoft mener??

Endret 2. juni 2009 av Slettet-t8fn5F