Package stalls on 1st step
New to PDQ and testing installs of Java 8. We use Faronic's Deep Freeze end point software to lock down our computers. Deep freeze has it's own command line protocol to executing commands to unlock computers running Deep Freeze.
So I took Java 8 Update package from the package library and added a step preceding all other steps in the package to thaw the machine shown below.
The issue I am having is that PDQ is hanging on the first step of unlocking the machine. The command is executed as I see that the machine is unlocked, but PDQ will not proceed to the next step. Any ideas?
0
Comments
I don't have any experience with Deep Freeze, but I found a blog post by Stephen Valdinger and he uses THAWNEXTBOOT instead of BOOTTHAWED.
I've been summoned!
Yes. I'd expect this behavior. /BOOTTHAWED tells the machine to reboot instantly into the thawed state. When that happens, you are severing the communication to the PDQ Deploy Runner service, and the deployment stops. You'll want to use /THAWNEXTBOOT, which will set the flag appropriately on the target machine. Your Reboot step which is next in line will reboot the machine, but in such a way that the runner service communicates back to the console that it has rebooted, and to move on to the next step.
For complete control of the process, at Step 13 I would add a command step to run dfc.exe with your password and the /FREEZENEXTBOOT argument, followed by another Reboot step. This will leave your machine in a FROZEN state, and the deployment will complete successfully.
I hope that wall of text makes sense and helps you.
Thanks for the reply. In step 1, I changed to /THAWNEXTBOOT and after the reboot in step 2, I see the target is thawed but the PDQ status is "Running (reconnecting)", which I'm sure is due to severing communication with the runner service.
Just a bit of background - The target computer has a DF version incorporating the a commandline password.
The Reboot step sometimes takes a little bit of time to complete I've noticed. It'll be Thawed in my DF console, but take ~45 additional seconds to 1.5 minutes to move to the next step. Is that what you are seeing? Or is it showing thawed in the DF console, and just never moving past (Reconnecting) at all in your Package step?
It reboots successfully and it's in a thawed state (per DF console) but does not proceed to step 3 and still disconnects the same way you mentioned in the for /BOOTTHAWED command.
Was there a resolution to this? I'm having this same issue...
Interesting behavior. Could you let me know what Version of Deep Freeze you are running?
Using the /THAWNEXTBOOT switch followed by a reboot step hangs the package
This happens on the first run of a package, but on subsequent runs the package completes smoothly and as expected.
Deepfreeze version is 8.22.220.4800
Super curious! I'm doing some digging on my end to see if I can come up with some logs that might be helpful. Standby.
Ok, I think we can take a look at a couple of logs. Can you provide the DF log for the trouble machine from the DF console?
Click this button:
Export as Txt so you can paste it here. Sanitize out the names, mac address, etc. I don't care about that.
Then could you check and see if a Service.log exists on the target computer at C:\windows\AdminArsenal\PDQDeployRunner? Sanitize and post that too.
I'll see if I can see anything glaringly wrong. Aside from that my advice would be to update Deep Freeze to the latest version, and get ahold of PDQ support (support@pdq.com). But I'll have a look first!
has anybody ever found a solution to this? I have the same problem. I invoke the /THAWNEXTBOOT command, followed by a reboot, the computer comes online, but pdq will not reconnect. I have to abort and restart the deployment. I have over 800 desktops with this configuration, so i need to be able to rely on the schedual option. I think it mainly happens after the computer is booted with a wake on lan.