-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppLayering: Layer finalize is blocked #38
Comments
Bugfix is required check MachineState 3 also |
add on Line 2276 BISF.psm1
|
implement in Bugs Bunny and developer branch |
Here you go, I can reproduce the problem on a new OS Layer. I would recommend they create their base OS Layer from the ISO with the minimum installed, import the layer into the ELM then introduce BIS-F in a version of the OS Layer. I don’t remember where I saw it but one of the original Unidesk engineers recommended creating an OS Layer with the ISO only and import that into the ELM. Create an image template linked to the initial OS Layer so the initial OS Layer from the ISO can never be deleted. Then do all your work off a version of the original OS Layer, including BIS-F and any optimizations. All App Layers are tied to the original OS Layer if for whatever reason you have to “start over” you can revert back to the original OS Layer without having to recreate all your App Layers. I don’t think BIS-F is properly identifying the original OS Layer install before importing into the ELM but based off what I said above I don’t know that it’s something you want to fix. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UniService] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UniService\VolEnum] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UniService\VolEnum\C] |
Cherry Pick and commit to https://github.com/EUCweb/BIS-F/blob/develop/Framework/SubCall/Global/BISF.psm1 |
if you prepare the VM step by step before import them into ELM and run BIS-F to finalize the image, BIS-F prompt the Error: Layer Finalized is blocked
29/03/2018 11:38:47 | Administrator | INFORMATION... | Processing function Test-BISFAppLayeringSoftware
29/03/2018 11:38:47 | Administrator | INFORMATION... | Processing function Test-BISFService
29/03/2018 11:38:47 | Administrator | INFORMATION... | Service UniService exists
29/03/2018 11:38:48 | Administrator | INFORMATION... | Product Citrix AppLayering (Version 4.9.0.74172) installed
29/03/2018 11:38:48 | Administrator | INFORMATION... | AppLayering MachineState is set to 3
29/03/2018 11:38:48 | Administrator | INFORMATION... | Processing function Test-BISFRegistryValue
29/03/2018 11:38:48 | Administrator | INFORMATION... | Registrypath HKLM:\SYSTEM\CurrentControlSet\Services\UniService, Value OSLayerEdit NOT exists !!
29/03/2018 11:38:48 | Administrator | INFORMATION... | Processing function Test-BISFRegistryValue
29/03/2018 11:38:48 | Administrator | INFORMATION... | Registrypath HKLM:\SYSTEM\CurrentControlSet\Services\UniService, Value VolumeSerialNumber NOT exists !!
29/03/2018 11:38:48 | Administrator | INFORMATION... | Processing function Test-BISFRegistryValue
29/03/2018 11:38:48 | Administrator | INFORMATION... | Registrypath HKLM:\SYSTEM\CurrentControlSet\Services\UniService, Value PrevBICTaskID NOT exists !!
29/03/2018 11:38:48 | Administrator | WARNING......... | Not defined - AppLayering MachineState is set to 3
The text was updated successfully, but these errors were encountered: