We've been testing out GSS3HF1 and we're seeing here an apparently random peculiarity with DAgent crashes. Machines when booting into WinPE5 will just sometimes have an agent crash as shown below,
Image may be NSFW.
Clik here to view.
We've opened a case with support, but it's puzzling.
I can deploy a machine a dozen times, and not see this. Then we'll get period where it happens with a high probability... then just as frustration peaks it vanishes again. This suggests an environmental factor creeping in that eludes me.
We've initiated thousands of deployments with the Altiris DS6.9 engine in this environment and have never seen this issue (we still have Altiris DS6.9 running in parallel to GSS and still no issues).
I know we aren't alone as I have another collegue in the UK report this for his new GSS installation too. One thing in common that we have is that GSS3 also seems to be automatically, though not consistently, resheduling jobs to 2071 on completion.
What I'm doing at the moment to track this is turn on agent logging in automation as per HOWTO:3066 and using WinCrashReport to collect crash data.
Environment Details,
- Fresh GSS3 install on a 2012 VM
- GSS install is a simple install
- No drivers added to automation, and no other tools added
- Clients are physical clients on the same subnet as the server.
- Have seen issue on various Dell models (9010, 760, 990), a Fujisu 420, and a Viglen Genie (whitebox hardware that's 100% intel inside).
- Clients are PXE booting
- No other software installed on Server (not even AV)
I've tried artificially loading the network and server to force this -all to no effect. I've also tried randomly disconnecting Agent comms -but all these outages are handled smoothly by the agent (which is a credit to it).
Anyone else seen this?
