I put this guide together a few months ago from some people that had never built a Ghost server before. We used Windows 2008 Server and Symantec Ghost Solution Suite 2.5.
The guide is written to a pretty basic level but it works. I have had 3 people built Ghost servers using this guide. I posted this because I have not found a great deal of information on building this server. This build used 3Com services, they are a little on the old side but they are included on the Ghost install disk. Also there may be other ways this is just how I do it.
Hope this helps someone. —–This guide assumes you have a Windows Server with DHCP installed ———- Installing Symantec Ghost Solution Suite 1.x or 2.x – Basic install defaults work for most situations. Install 3com Services – Defaults work for everything except you should select server when the install comes to the following screen. Selecting Server installs every part of the 3Com services. Add Option 60 to DHCP Server – This is not a default option and has to be added manually. Open command prompt as Administrator.
Enter netsh.exe dhcp server add optiondef 60 “Class ID” string 0 PXEClient. Enter netsh.exe dhcp server set optionvalue 60 string PXEClient.
Exit the command window and restart the DHCP service Creating Boot Image. Open Symantec Ghost Boot Wizard 2. Select PC-DOS 3. Select TCP/IP Network Boot Image 4. Select Universal Packet Driver v2.0 – Additional drivers can be added here, and you can see all the current drivers by selecting the show all drivers check box. Click next until you come to the following screen. Browse for the location and enter the name you want for the file.
Click Next and then Finish. Creating PXE Menus Boot file. Open 3Com Boot Image Editor 2.
Select Create PXE menu boot file 3. Select Add 4. Click Browse and select the boot image file and click ok 5. Click save and name the file Create Bootptab file. Open 3Com Bootptab Editor. Select new 3. Select add 4.
Wide Area Network
Enter Name, fill Node box with question marks, and select PXE Menu file you created. Click OK when finished. Save file as Bootptab If your network is configured you should be able to ghost images across the network. Changes can be made and there is still the possibility of errors. Such as the PXE-E79, NBP is too big error. This can be fixed by playing with the Bootptab file.
This guide will get you setup but may require a few tweaks to fix any errors that may show up. If you choose to boot in to a PE image you can do that with these simple steps. The previous instructions are for a PCDOS PXEboot.
To do this you get rid of option 60 and add options 66 and 67. Option 66 is the boot servers name or IP address and 67 is the boot file name and location. You do everything the same except you build a PE image instead of a PCDOS images. Then add the two options to your DHCP server options. Once again in 66 you add your boot server IP and in 67 you add the path to the boot file location. You will leave off the TFTPBOOT folder part of the path.
Because it will look there by default. The file you put in there sill be PXEboot.n12 if it was made with the Ghost image builder. Then it will boot into a screen that looks like the following. The Ghost menu will pop up and you will be ready to go. You can also use a Linux boot image with this style of PXEboot by adding your Linux image into the TFTPBoot folder and adding that path into option 67.
The file it boots will usually be pxelinux.0 or something similar. I have had problems using this way for ghosting certain machines because the PE environment didn’t have the correct drivers for the hardware.
So I usually use PCDOS. I just thought I would add this in there for people that want to try something different. First lets start with the time it takes to send out an image.
Magic workstation free download mac. We imaged about 300 computers a few weeks ago and an image that was 23 gig took 45 minutes on a 1 GigaBit LAN. We were also sending it out to about 100 computers. As for the multicasting, we use multicasting when ghosting more than a few computers.
The other ways are Unicasting or a Directed Broadcast. Unicast is only good for a few computers, so you will have to do a Directed Broadcast. I have never used this mode before so I can’t say what will change in the time it takes to send out the image. If I am not mistaken it is an option when you log into the ghost session to select this mode. However depending on the version you have it may be a little different.
Hi guys, we have a problem with network management in the guest virtual machines with Windows Server 2008. We have created a VM with WinSrv 2008, we have deleted it leaving the vhd because we had to move it in another partition, but when we create a new VM attaching its original vhd WinSrv 2008 shows 3 network interface inside the guest OS (2 of which are hidden and not viewable in the device manager even with the 'show hidden device' option) and the device manager create a new network adapter with the name 'Microsoft Virtual Machine Bus Network Adapter #3'.
With a guest VM with WinSrv 2003 the behavior is different and the device manager shows only one interface with the default name 'Microsoft Virtual Machine Bus Network Adapter'. How can we remove these hidden/ghost interfaces? We hope you can help us quickly because next week this virtual environment should be perfectly working. Have a nice day.
Hi, It seems that the network adapter has been removed from the device manager, but some registry entry still remained in the registry. Please try this KB. The DevCon utility is a command-line utility that acts as an alternative to Device Manager. When you use DevCon, you can enable, disable, restart, update, remove, and query individual devices or groups of devices. To use DevCon, follow these steps:. Download the DevCon tool by clicking the following article number to view the article in the Microsoft Knowledge Base: The DevCon command-line utility functions as an alternative to Device Manager.
Unpack the 32-bit or 64-bit DevCon tool binary to a local folder. Click Start, click Run, then type cmd and press ENTER. Type CD: pathtobinaries to navigate to the devcon.exe is located. Use the following syntax to find installed network adapters: devcon findall =net or devcon listclass net Note In the output of the previous commands, there is a line for the ghosted network adapter that is similar to the following: PCI VEN10B7&DEV9200&SUBSYS00D81028&REV78 4&19FD8D60&0&58F0: 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible). Remove the ghosted device by typing the following syntax: devcon -r remove '@PCI VEN10B7&DEV9200&SUBSYS00D81028&REV78 4&19FD8D60&0&58F0' Vincent Hu.
If is it possible I'd like to receive another little help;-) this tip works perfect with all of mine VM except of one. I think to have done some bad configuration trying to solve this problem. In the device manager I have only one network adapter called: Microsoft Virtual Machine Bus Network Adapter but tools like bginfo (that do a wmi query) shows me 3 MAC address and 3 NICs.
How is it possible? Some wrong key in the registry? Do you have some suggestions? Thanks in advance. Have a nice work! Interface index 1 is a pseudo-interface that is used for loopback (named the Loopback Pseudo-Interface). Interface index 2 is a pseudo-interface that is used for the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) IPv6 transition technology (named the Automatic Tunneling Pseudo-Interface).
Interface index 3 is a pseudo-interface that is used for 6to4 tunneling (named the 6to4 Tunneling Pseudo-Interface). Other interfaces are numbered sequentially in the order in which they are created. This order varies among computers. Why do I have an 'Automatic Tunneling Pseudo-Interface' interface?
IPv6 in Windows XP and Windows Server 2003 uses the 'Automatic Tunneling Pseudo-Interface' for encapsulating IPv6 packets with an IPv4 header so that they can be sent across an IPv4 network. By default, IPv6 configures a link-local Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) address on the Automatic Tunneling Pseudo-Interface. The link-local ISATAP address has the form fe80::200:5efe:w.x.y.x or fe80::5efe:w.x.y.x, in which w.x.y.x is an IPv4 address assigned to the computer. How do I disable IPv6 in Windows Vista and Windows Server 2008? Unlike Windows XP and Windows Server 2003, IPv6 in Windows Vista and Windows Server 2008 cannot be uninstalled.
However, you can disable IPv6 in Windows Vista and Windows Server 2008 by doing one of the following. Mmmm, it's very difficult for me to understand why I have only one ethernet connection in bginfo in all VM with WinSrv2k8 except of this. I don't think that it's something about ipv6 because I disabled it on all our VM.
I really think that it's caused by some of my wrong configurations but I don't know what. Obviously with the custom parameter (WMI query), bginfo shows me the correct informations.
I knew this tip and I used it for teaming network interfaces;-) but in this situation I cannot understand where OS reads these ghost parameters. I repeat: all seems to work good, it's only a 'visual' problem, but I'm very curious to understand what is causing this behavior. Thanks again. Hi, It seems that the network adapter has been removed from the device manager, but some registry entry still remained in the registry. Please try this KB. The DevCon utility is a command-line utility that acts as an alternative to Device Manager. When you use DevCon, you can enable, disable, restart, update, remove, and query individual devices or groups of devices.
To use DevCon, follow these steps:. Download the DevCon tool by clicking the following article number to view the article in the Microsoft Knowledge Base: The DevCon command-line utility functions as an alternative to Device Manager. Unpack the 32-bit or 64-bit DevCon tool binary to a local folder. Click Start, click Run, then type cmd and press ENTER. Type CD: pathtobinaries to navigate to the devcon.exe is located. Use the following syntax to find installed network adapters: devcon findall =net or devcon listclass net Note In the output of the previous commands, there is a line for the ghosted network adapter that is similar to the following: PCI VEN10B7&DEV9200&SUBSYS00D81028&REV78 4&19FD8D60&0&58F0: 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible).
Remove the ghosted device by typing the following syntax: devcon -r remove '@PCI VEN10B7&DEV9200&SUBSYS00D81028&REV78 4&19FD8D60&0&58F0' Vincent Hu. Hello Vincent, I have the same problem. The Bginfo.exe utility displays 2 Microsoft Virtual Machine Bus Network Adapters (only last is populated with IPv4 info). The Divice Manager is clean; no hidden network adapters. The registry appears to be clean. Yet, Bginfo reads a ghost adapter and its MAC address from somewhere.
It is definitely not from the relevant WMI classes. I manually queried Win32NetworkAdapter and Win32NetworkAdapterConfiguration and found that all instances are accounted for.
I also used the Devcon.exe utility to no avail. It list everything that I can see in the Device Manager and/or the registry. The MAC address that is assigned to the ghosted adapter confirms that it was a previously emulated Microsoft Virtual Machine Bus Network Adapter. If you can find out from where the Bginfo.exe utility reads the default, or information, we can quickly locate the stale data. Please let me know.
Description Type OS Version Date This download record installs version 22.10 of the administrative tools for Intel® Network Adapters. Software Applications OS Independent 22.10 Latest 12/7/2017 This download record installs version 22.10 of the Intel® Ethernet Adapter drivers for MS-DOS. Drivers DOS 22.10 Latest 12/7/2017 This download record provides 22.10 release notes and the Intel® Ethernet Adapters user guide. Documentation OS Independent 22.10 Latest 12/7/2017 This download installs version 22.10 of the Intel® Ethernet Adapter Complete Driver Pack for supported versions of Windows., Linux., and FreeBSD.
Drivers OS Independent 22.10 Latest 12/7/2017 This download version 22.10 installs UEFI drivers, Intel® Boot Agent, and Intel® iSCSI Remote Boot images to program the PCI option ROM flash image and update flash configuration options. Software Applications OS Independent 22.10 Latest 12/7/2017 Disabling TCP-IPv6 Checksum Offload Capability with Intel® 1/10 GbE Controllers Drivers OS Independent 1.0 Latest This download includes version 7.6.2 of the gigabit base driver for Intel® Network Connections. Drivers Linux.
7.6.2 Latest 5/20/2016 This download installs version 18.4 of the Intel® Network Adapter for Windows. Vista. Drivers Windows Vista. Windows Vista 32. Windows Vista 64. 18.4 Latest 7/19/2013 This download installs the Intel® Network Adapters driver version 18.4 for Windows Server 2008.
Drivers Windows Server 2008. Windows Server 2008 Datacenter x64 Edition. Windows Server 2008 Enterprise x64 Edition. 2 more 18.4 Latest 7/19/2013 Installs network drivers.
Includes Intel® PROSet for Windows Device Manager., advanced networking services (ANS) for teaming and VLANs, and SNMP. Drivers Windows XP. Windows XP Professional x64 Edition. 18.3 Latest 5/15/2013 This download installs Intel® Network Adapters drivers version 18.3 for Windows Server 2003. Drivers Windows Server 2003.
Windows Server 2003 Enterprise x64 Edition. Windows Server 2003 for Itanium-based Systems.
Windows Server 2003 Standard x64 Edition. 18.3 Latest 5/15/2013 Gigabit Linux. base driver for Intel® PRO/1000 PCI and PCI-X family of adapters Drivers Linux. 8.0.35 Latest This Linux. shell script displays your network devices' Name, Device ID, Driver Name, and Driver Version.
Software Applications Linux. 1.0 Latest 1/16/2009 Installs Network Adapter Drivers and Intel® PROSet for Device Manager only on Intel® Itanium® processor based systems. Drivers Windows XP 64-bit Edition. 11.2 Latest FreeBSD. base driver for the Intel® PRO/1000 Family of Adapters.
Drivers FreeBSD. 4.1.6 Latest 3/13/2006 Intel® PRO Network Adapters base driver release 10.01 plus Intel® PROSet II for Windows NT. 4.0. This is the final release for Windows NT 4.0. Drivers Windows NT 4.0. Windows NT Terminal Server.
10.01 Latest DMI v2.0 Network Adapter Instrumentation for Windows. Add-ons & Plug-ins Windows NT 4.0. Windows NT Terminal Server. 10.0 Latest 5/26/2005 Windows. Management Interface provider for NICs, Boot Agent and Quality of Service (QoS). Intel® PROSet provides this for Windows. Serial key.
2000, 2003, and XP. Add-ons & Plug-ins Windows NT 4.0.
Windows NT Terminal Server. 10.0 Latest 5/26/2005 Supports current and legacy DOS and OS/2. clients, & clients used by some disk imaging programs.
Now includes instructions for Symantec Ghost. Drivers DOS OS/2. Novell ODI. 10.2 Latest 5/4/2005 Adds IEEE 802.1p and QoS tagging/filtering user interface to Intel® PRO/100 and Intel® PRO/1000 LAN adapters. Not needed to use native OS QoS.
Add-ons & Plug-ins Windows XP Professional. Windows Server 2003. Windows Server 2003 Standard Edition. 3 more 10.0 Latest 5/2/2005.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |