If you kill the process or reboot in the middle, you might wind up with partially written. Don't reboot or you might cause it to have to start over. Or you can wait it out, and run "ngen queue status" periodically to see how it's doing, but that will slow it down because the background process pauses every time you check its status in the foreground. To watch it in the foreground, run "ngen update /force". Generally this is simply true: the ngen rebuild is still running. Net assemblies are compiled into native images) is still in progress. "A Microsoft NGen operation is in progress in the background" is telling you that a foreground or background NGEN operation (where. If, after cleaning out the top three, you still get the prompt on reboot, you will need to use the flag to ignore layer integrity checks. I've seen some software modify the NETLOGON\Start key on every reboot, so maybe that's happening. HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\COMPUTERNAME\COMPUTERNAME HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\COMPUTERNAME\ACTIVECOMPUTERNAME HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\NETLOGON\Start This is how we determine that a domain-join operation is still waiting for a reboot. Then we look for changes in the NetLogon key (if the current value is now different from what it was at bootup), and to see if the computer name doesn't match the active computer name. You can manually modify any of these to suit your needs, including just deleting them. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations It may also be helpful, if the problem is NetLogon, to restart the Unidesk Service for Message Management.įirst we check for the existence of any of these three: Your first course of action should be to reboot, more than once(in some cases it has taken 3+ reboots), just to make sure that it isn't a real reboot being requested by some software. "A post-installation reboot is pending" is looking at six different registry keys. You can manually run the referenced script and delete the key, or just delete the key if the script file no longer exists. Windows normally deletes those keys on reboot, but we have seen circumstances (especially with our own script, envsetup.cmd) where that doesn't happen. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnce HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce "A RunOnce script is outstanding" is telling you that there is a key in either of these two locations: "FSLogix driver is configured to run but the altitude is not set to 138010 - please check and reboot the packaging machine" "Software Center Client is configured to run, but the SMSCFG.INI is still present. "a reboot is pending to update drivers on the boot disk - please check and reboot the Packaging Machine" "an MSI install operation is in progress - please check the Packaging Machine" "a Microsoft NGen operation is in progress in the background " "a post-installation reboot is pending - please check and reboot the Packaging Machine" "a RunOnce script is outstanding - please check and reboot the Packaging Machine" There are 8 Layer Integrity warnings you can see: But it's still a valid way to give up and bypass it. The registry key, noted at the end of this article, to bypass or ignore integrity problems still works, and you should be just as reluctant to use it as ever. You must successfully run that Shutdown for Finalize script to finalize a layer. But if you try, you will find the ELM will stop the task and return you to the Packaging Machine, because it knows that the Layer Integrity Checks either failed or never ran. You might think you could bypass the Layer Integrity check by just shutting down the machine normally and finalizing that. You can't know exactly which UniBilcLogs file it's using, so look for the one with the latest timestamp. It also writes this information into two log files:Ĭ:\Program Files\Unidesk\Uniservice\Log\LayerIntegrity.txtĬ:\Program Files\Unidesk\Uniservice\Log\UniBilcLogs_X.txt Fix the issue (for instance, reboot) and try again. If something is, it does not shut down, and instead puts up a statement about the pending issue. Shutdown for Finalize is checking to see if anything is still pending that should happen in the layer rather than happen in the image later. Uniservice is tracking all the same things it always has for Layer Integrity: NGEN or MSCORLIB is still running, a reboot is pending, a domain operation is still pending, or a RunOnce script is still waiting. It makes a call to uniservice.exe to get the current Layer Integrity state. In V4, when you're ready to shutdown and finalize a layer, you run the Shutdown for Finalize icon on the desktop (As Administrator).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |