Ghost Solution Suite

Hello,

I'm facing a big problem, it's now 2 times that when imaging multiple computers some (like nearly all) of them at some point of the configuration task get their DHCP Client service deactivated. The result is computer with random names "win-etc", joined to the domain (but they are not realy joined).

If i put the DHCP Client service on automatic start and reboot the task will try to do the configuration but will fail with "network path not found error code 53".

I realy don't understand what's going on, i had 42 computers done without any trouble and now for 40 computers only 13 had been succesfull :(

The task is a imaging one + deployanywhere + configuration.

Thx in advance.

For error code 53 my notes say "Network name not found. Check Port 137 (UDP), 138 (UDP) and 139 (TCP) are open."

I'm going crazy, if I relaunch the same task on the same computers i got a 50-50 chance of the task working perfectly.

In c:\windows\debut\netsetup.log

Working computer :

07/19/2016 11:28:48:374 -----------------------------------------------------------------
07/19/2016 11:28:48:374 NetpUnJoinDomain: unjoin from 'xxx' using '(null)' creds, options: 0x0
07/19/2016 11:28:48:381     OS Version: 6.1
07/19/2016 11:28:48:381     Build number: 7601 (7601.win7sp1_ldr.160408-2045)
07/19/2016 11:28:48:381     ServicePack: Service Pack 1
07/19/2016 11:28:48:382     SKU: Windows 7 Professionnel N
07/19/2016 11:28:48:382 NetpUnJoinDomain: status of getting computer name: 0x0
07/19/2016 11:28:48:382 NetpApplyJoinState: actions: 0x2b005a
07/19/2016 11:28:50:383 NetpApplyJoinState: status of stopping and setting start type of Netlogon to 16: 0x0
07/19/2016 11:28:50:430 NetpApplyJoinState: NON FATAL: status of removing DNS registrations: 0x6ba
07/19/2016 11:28:50:430 NetpGetLsaPrimaryDomain: status: 0x0
07/19/2016 11:28:50:431 NetpLsaOpenSecret: status: 0x0
07/19/2016 11:28:50:431 NetpLsaOpenSecret: status: 0x0
07/19/2016 11:28:51:524 NetpSetLsaPrimaryDomain: for 'xxx' status: 0x0
07/19/2016 11:28:51:524 NetpApplyJoinState: status of setting LSA pri. domain: 0x0
07/19/2016 11:28:52:832 NetpApplyJoinState: status of clearing ComputerNamePhysicalDnsDomain: 0x0
07/19/2016 11:28:52:832 NetpManageLocalGroups: Populating list of account SIDs.
07/19/2016 11:28:54:615 NetpApplyJoinState: status of removing from local groups: 0x0
07/19/2016 11:28:54:617 NetpUpdateW32timeConfig: 0x0
07/19/2016 11:28:54:619 NetpUnJoinDomain: status: 0x0
07/19/2016 11:28:54:781 -----------------------------------------------------------------
etc etc renaming, joining domain.

On a not working computer :

07/19/2016 15:31:05:769 -----------------------------------------------------------------
07/19/2016 15:31:05:770 NetpUnJoinDomain: unjoin from 'xxx' using '(null)' creds, options: 0x0
07/19/2016 15:31:05:819     OS Version: 6.1
07/19/2016 15:31:05:819     Build number: 7601 (7601.win7sp1_ldr.160408-2045)
07/19/2016 15:31:05:819     ServicePack: Service Pack 1
07/19/2016 15:31:06:458 [000003a0] NetpGetLsaPrimaryDomain: status: 0x0
07/19/2016 15:31:10:737     SKU: Windows 7 Professionnel N
07/19/2016 15:31:10:737 NetpUnJoinDomain: status of getting computer name: 0x0
07/19/2016 15:31:10:737 NetpApplyJoinState: actions: 0x2b005a
07/19/2016 15:31:11:764 NetpApplyJoinState: status of stopping and setting start type of Netlogon to 16: 0x45b
07/19/2016 15:31:11:764 NetpApplyJoinState: initiating a rollback due to earlier errors
07/19/2016 15:31:11:764 NetpApplyJoinState: actions: 0x40000
07/19/2016 15:31:11:764 NetpGetLsaPrimaryDomain: status: 0x0
07/19/2016 15:31:11:764 NetpUnJoinDomain: status: 0x45b

This has all the hallmarks of a timing issue.  Can you add a delay into any operations that involve mounting the network driver and subsequently trying to use the network driver ?  I line with this, can you check that you have the latest driver installed for your NIC into WinPE ?

Can you also check that the WInPE firewall is switched off and read Andykn101's post and respond to it ?

I also saw this symptom of the agent disabling the DHCP service on client machines after an image was deployed. I found that if you are willing to wait long enough (and I mean along time, maybe 45 minutes) it will eventually come good and carry on with the config task. As an alternative, I also found that if I manually re-enabled and started the DHCP service, that would move things along. On the same machines, I also had a weird 17 minute delay after every reboot before the client would communicate with the console (all other communication was normal, no issues browsing local network resources etc etc).

As for drivers, I was using the same PXE/PreOS for Win7 and Win10 builds on the same machines...Win10 is just fine thanks so it can't be drivers.

I did NOT find the cause as such, but the cure for those particular issues was to start a fresh Win7 install on the machines baed on the product recovery disks, rather than using the as-supplied fresh from HP Win7 install complete with bloatware.

 

FWIW, I never got a single response as to why the agent messes with DHCP like that when the job is defined for DHCP. I didn't bother trying it out with a manually defined IP address, but that might be worth trying??

 

My world of GSS3 pain has centred around HP450G3 laptops with SSDs. These thigns really DO NOT get along with Win7/GSS3.x  I'm still struggling now with what feels like random problems cropping up every time I think I've got it gripped.

 

Good luck finding a resolution.