I just recently downloaded the official trial version today and noticed that there's no longer create an image as VHD or VMDK. The only option is .GHO. Is that option officially out? The option was available in the first Beta version and when I contacted support they said that it was disabled in Beta. We are now live and the option to save an image as .vhd is no longer available. Anyone know what happened to that feature? Thank you!

Dear All,

I have a VMWare ESX 5.5 server and I need to create a Windows 7 x86 machine that uses a VMXNet 3 NIC. I have an image from another PC, ready to be deployed.

I harvested the VMXNet 3 driver from a working Windows 7 x32 VM machine and uploaded it into GSS 3.0 and regenerated the WinPE Boot option. I can see the drivers (x86 and x64) in the drivers list and in the file system. I can also see the files in the "\Windows\System32\DriverStore\FileRepository" of the Boot.wim.

When the VM machine boots up, I still get the dreaded DHCP message. If I change the NIC to N1000, then the WinPE works.

I need to create a machine with the VMXNet 3 NIC, but WinPE does not work with this driver.

Can anyone help me, please?

Kindest regards,

QuietLeni

I am trying to find a way to install the Ghost 3.0 CLient agent on to an image so that after image is pushed, the client will show up in the Ghost 3.0 console.  I do not find a way to add it to an image as I used to be able to do in GSS 2.5 by installing a Ghost Console Client.

Thanks in advance

Art

Just performed a fresh install of GSS 3.0 followed by HF1 on a new machine trying to migrate away from GSS 2.5.1.  My lab already has Windows 7 64-bit installed and running perfectly.  I've successfully installed the Agent and it is reporting to my GSS console correctly.  I've recently updated one of my machines and need to push this image out to the rest of the machines.  I don't have PXE setup or available so I thought I would use the Automation Partition, but have had no success.

I've successfully installed the Automation Partition to the "source" workstation and it boots into Automation successfully, but then hangs trying to get an IP address.  The machine throws "Validating network connection (criteria = -169.254)..." followed by a loop of "Restarting DHCP client service: retry 1-19".  Followed with "Could not acquire IP address".

The process continues and eventually the agent loads but displays "Connect failed".

If I bring up one of the minimized command windows and run a "ipconfig /all" the network adapter does display and shows an APIPA address.  In previous versions of GSS, if you run "ipconfig /all" and the driver wasn't loaded the NIC wouldn't display at all let alone an APIPA address.  If I try to run an "ipconfig /release" followed by "ipconfig /renew" the renew command will just hang or I'll receive a message that "The Interface is Unknown".

Thinking there was something wrong with the Automation Partition, or the way I created it, I went through to try to create a bootable USB media using the instructions I found here: http://www.symantec.com/connect/articles/creating-boot-media-legacy-ghostcasting-ghost-solution-suite-3.  Unfortunately, when I connected the drive to a workstation I receive the same results.

I've been fighting this all day now and am at my wits end.  I've read multiple articles on this that seem to indicate a driver issue.  Most are related to VMware so I downloaded the entire Intel driver collection, the target NIC is an Intel i217-LM, and added it to the DeployAnywhere Driver Database.  Still no love.  Can someone point me in the right direction to hopefully get this resolved?

Thanks!

We've just recently got GSS 3.0 up and running on Windows Serve 2012, and it is generally working pretty smoothly.

One issue, though: The agent on the machines only become visible to the server if a user is logged in. It would be nice if the machine was immediately visible when Windows is booted up and waiting at the login screen as well as when a user is logged in. Is this possible? Thanks in advance for any help.

Dear Symantec,

When I import the VMXNet3 (and other ESXi 5.5 drivers) into DA within GSS 3.0, it seems to have imported the driver, but the driver seems not to be picked up by Windows. I have been running around in ever-decreasing circles, until I found this in the DriversDB Driver Manifest file:

{
    "VMXNet3" = {
        class = network,
        drivers = ({
            path = "VMXNet3\\vmxnet3ndis6.inf",
            devices = {
                0x15ad = {
                    0x7b0 = (-0x1)
                }
            },
            os = ("2003""2008""VISTA""WINDOWS7""WINDOWS8""WINDOWS8_1""X64_2003""X64_2008""X64_2008_R2""X64_2012""X64_2012_R2""X64_VISTA""X64_WINDOWS7""X64_WINDOWS8""X64_WINDOWS8_1""X64_XP""XP"),
            architecture = (X86 AMD64),
            files = ("vmxnet3ndis6.inf""vmxnet3n61x86.sys""vmxnet3n61x64.sys""vmxnet3ndis6.cat")
        }),
        internal = 0
    }
}

All seems to be OK, but I noticed that all of the affected drivers have the following line:

                    0x7b0 = (-0x1)

Which I think (-0x1) looks like a NULL value!

Is the driver being uploaded improperly? What should the right value to the right of the equals and is there a fix to this?

I see no fixes for this in the HF1 and I am loathe to upgrade if there is not an issue that can be fixed with a patch.

Kindest regards,

QuietLeni

Hello,

We are using Altiris 6.9 SP5 build 574.

We use Altiris for managing our Thin Clients from HP T5730 and T5740.

The new Thin Clients from HP he T500 and T600 series are not supported anymore with 6.9.

In GSS 3.0 I see that Thin Clients are supported, but i cannot see which Thin Clients.

I an worried about WES 7 and WES 8 support and MS EWF on the new HP Thin clients.

We also have problems with the PXE config in our Windows 2012 DHCP Failover config on multiple sites.

Is GSS 3.0 the right choice for us ?

Hans.

We want to establish the best practice regarding deploying Ghost Solution Suite across multiple locations with relatively slow network links between them.

Lets say that you have a corporate office that has computers to image locally but is also responsible for imaging computers at several remote sites.  These remote sites have links that are adequate for management traffic, but would not be optimal for streaming entire system image files across.  

You have the server, database, and file shares with all of your image files located in the corporate office.  What is the best way to have duplicate copies of the image files local at the sites so that you can initiate the image process for all the sites from a central console, but specify that the image for each system will come from a local storage repository or ghost server.  

1. Is this possible?  If so, is there a doc anywhere on how to configure it this way?

2. If it is possible, does it include an automated function to deliver the image file 1 time when it is created to the remote sites, or would you have to manually copy the image file to each of these servers or set up some sort of file synchronization tool?

Thanks very much in advance for your insight.

Hi,

Just wondering if the automation partition not being compatible with UEFI hardware has been fixed in HF1 for Ghost 3.0? If not, what is the timeline for this? In our environment it is crucial in order for us to deploy Ghost 3 into production as we can't use PXE in our environment.

Cheers,

bustech

Several client machines are regularly getting stuck on an Agent Update job, and that prevents them from running other jobs (interruption of daily scheduled jobs is especially annoying).

The status of these stuck jobs is "Brokered request at <date and time>".

I am having so many issues with PXE Booting that I hardely know where to begin.  I've made it far enough that now the machine is able to see the PXE server but thats as far as I've got.  The issue I am having now is that the client computer is looking in the wrong place for the boot file.  The DHCP Option 67 is set to BStrap\x64\BStrap.0 but the file that it shows in the log that the client is attempting to download is BStrapd\BStrap.0 for some reason.  The same goes for the x86 version, DHCP Option 67 set to BStrap\x86pc\BStrap.0 but client is looking for BStrap†pc\BStrap.0.  So I figured I'd just put the BStrap.0 file in to a folder called BStrapd or BStrap†pc and that got me further but then the client machine throws an error: PXEPreZero: Invalid PXE Server list format and thats where I'm stuck.  I don't know how to procede from here.  Any help would be much appreciated!

Hello,

I have been using GhostCast Server to pull ghost images from a Window 2008 Server for years. We run Ghost on the client system and have a WATTCP.CFG file that specifies an IP address to connect from (172.x.x.x address). We can ghost across subnets by specifying the server IP address in “Discovery Method”, or use the “automatic setting when we use a (172.x.x.x) address when we are on the same side of the switch (I have two NICs in the server). I now have setup a Windows Server 2012 R2 server and have installed Ghost solution suite 2.5 (same as 2008 server). I again configured 2 NICs, one with a standard static IPon that subnet, and one with a 172.x.x.x address. If we are on the same subnet I can pull the images fine using the “automatic” setting, but when we try to pull an image across the network by specifying the server IP address in the “Discovery Method” section of the GhostCast Server it never connects and fails with an error 10030. The GHOSTERR.TXT file specifies a 19932 error. This is obviously an issue with my Server 2012 R2 settings, as everything is configured the same on both servers in regards to the Ghost Solution Suite and GhostCast Server, and it works on Server 2008, but not Server 2012. Any ideas? Is there a port I may need to open that is closed by default on Server 2012? Again, I CAN pull images from the new server if I am on the same side of the switch AND use a 172.x.x.x address instead of a standard address on the subnet. Any help is greatly appreciated.

Thanks in advance.

We are having an issue with our new Ghost 3 Server and PXE Booting.

For the most part PXE booting works just fine. However we have discovered one major issue. If we PXE Boot a computer and it has a job assigned to it like connecting to a Ghost Cast session the first time we boot it will connect just fine and load up and wait for Ghost Cast Session to start. However if for some reason we need to reboot that computer to have it reconnect when we try and PXE Boot the computer a second time we get the PXE menu but as soon as we select a menu item it starts to load and almost immediately we are given a blank blue screen with no error message and system just hangs there. If we try to PXE Boot again it just reoccurs.

We have not found a consistent solution to solve this problem. We have tried to stop all active jobs and reschedule them, we have deleted computer from console and we have tried to restart the Ghost Server.  We have had some of these solutions work at times but not consistently.

Any ideas on what is causing this and how to fix the problem or prevent it from occurring altogether would be great.

Thanks

Bonjour,

je suis utilisateur depuis une 10aine d'années du logiciel Ghost pour gérer les salles de cours que je gère. Environ 200 ordinateurs dans différentes salles. Mais depuis 4-5 jours que je teste la version 3.0, je suis extrémement déçu par cette nouvelle version.

Plusieurs fonctionnalités ont tout simplement disparu on dirait.

Via le client, il ne semble même plus possible de voir une liste des tâches en cours ou récentes (Dans GSS 2.5 le "Active Task Pane").

Lorsqu'on lance une tâche, on a plus la fenêtre GhostCast Server qui s'affiche donc plus moyen de savoir où on en est dans l'avancement de la tâche (est-ce qu'il reste 1h, 2h, 3h, ...).

Via l'interface, plus moyen de voir la liste des images dont on dispose ... Il semble avoir quelque chose lorsqu'on active Affichage > Activer la vue Client Léger mais alors je ne vois plus les ordinateurs que je vois dans l'interface classique.

Créer une tâche de configuration (par exemple, remettre un ordinateur dans l'Active Directory, sans devoir redéployer toute l'image), pas encore trouver comment.

Devoir ré-utiliser une boot partition qu'on doit installer via une tâche séparée alors que ça avait disparu auparavant (Etape "Copying/Updating PreOS files" qui était faite automatiquement avec GSS 2.5).

Sans parler d'une interface graphique et d'iĉones digne du début des années 2000.

Surement d'autres choses que je n'ai pas encore constaté ...

Bref, ça ressemble plus à un retour en arrière qu'à une évolution... Il ne me reste plus qu'à tester d'autres logiciels

Happens after I get GSS 3.0 (Build 1252) w/ HF1 installed on either Windows 2008 R2 or Windows 2012 R2 servers.  Everything is installed from scratch. I get the following errors in Event Log:

Faulting application name: axengine.exe, version: 13.0.0.1252, time stamp: 0x5582e11d
Faulting module name: LIBEAY32.dll, version: 1.0.1.13, time stamp: 0x550fd33b
Exception code: 0xc0000005
Fault offset: 0x0007b697
Faulting process id: 0xd5c
Faulting application start time: 0x01d0c87e9cf90044
Faulting application path: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\axengine.exe
Faulting module path: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\LIBEAY32.dll
Report Id: 51762c36-347a-11e5-a732-001ec9f707d6

Faulting application name: axengine.exe, version: 13.0.0.1252, time stamp: 0x5582e11d
Faulting module name: ntdll.dll, version: 6.1.7601.18869, time stamp: 0x55636317
Exception code: 0xc0000374
Fault offset: 0x000cea5f
Faulting process id: 0xa20
Faulting application start time: 0x01d0c887648daa83
Faulting application path: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\axengine.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: c3167e72-347a-11e5-a732-001ec9f707d6

Error:  OpenSSL public and private keys do not match.

Anyone have any ideas?

I'm pretty new at deployment stuff so please excuse my ignorance.

Company wants me to be able to remotely image and re-image our workstations. We have about 200 client systems we'd like to manage this way. At present I've inherited a 2.5 environment that I can't seem to get the new machine NIC drivers into a new boot disk so decided to try out PXE boot with GSS 3.0.

It's taken me a few days but I have the trial installed, PXE configuration set up and remote agents installed onto the OS only new system. I can start a new Job and it reboots the client, client boots into PXE, seems to find the DHCP server but fails with TFTP Timeout error PXE-032. There is a previous post on forums with basically exact same screen shot, his/her solution was to change the PXE server configuration to "Third party DHCP", I've tried this also.

PXE Server, TFTP are on the same server as GSS.
DHCP and Ghost servers are on the same subnet/vlan.
Network Engineer has said they aren't blocking anything, (referring to the ports ghost uses, will have to confirm 100% but so far he's said nothing is being blocked internally)

So far I have made the following configurations:

Added 66 and 67 in DHCP.
PXE Configuration Utility:
"no DHCP server installed on PXE server (use DHCP port)" is checked, but a post on forums stated "Third party DHCP" should be checked despite it not being the case, I've tried both options.
"Enable response to request from computers not in the GSS Database" checked
Status Tab has all services green

I've added MTFTP server service as dependent on PXE server service as another post has suggested.

I've changed many options in PXE Configuration but get the same TFTP timeout error. I did try a cmd line TFTP server test to pull the Strap.0 file. There is code at the top then a bunch of errors, not sure if any of it is useful.

Thank you in advance for your time and assistance.

Probably something very easy but we cannot figure out the ADK stuff. We have downloaded the kit but when installing Ghost it asks to point to where it is. it appears to be looking for an exe file and the only one I see is the downloaded adksetup.exe we got from microsoft. All we want to do is make images of our machines here. We are able to find the computers on the network, install the client software from ghost but when it comes time to image we are stuck.

Any help would be great!

Thanks,

Mike

I ordered some addtional GSS licenses for my GSS25 system.  They were GSS30 license.  When I tried to add the *.slf file I received the following error:

A licensing error occurred:

No licenses exist for Symantec Ghost Solution Suite (0x80000013)

Is there a way I can use the 3.0 licenses with my 2.5 system?  ..an easy way?

Thank you

Hi All,

I am looking to use GSS 3.0 to deploy OS's & Images to my Exisiting Laptop Fleet and any new devices that we aquire.

These laptops are required to run Bitlocker to protect the systems whilst travelling.

Bitlocker is configured to use and external USB Key and to require a PIN before the user can start their system.

I need to repartition the client disk drive before deployment to remove any existing Bitlocker protection.

How can i do this?

Also, is it possible to modify client BIOS Settings from GSS , specifically Dell BIOS Passwords to secure them.

Thanks in advance

Mike Kennedy

Hi, I'm trying to get my computer laboratory joined in our domain and getting the Windows activated. None of those works at the moment.

For the domain, I set "Configuration modification" task with the domain name in it. When I log my computer with a local account, I see that the compter is joined to the domain, but I cannot log in with any domain account. I don't see the computer in the domain too.

As for the licence, I tried in the same "Modify configuration" task and also with a script, not working either. 

Am I missing something?