Updated to 3.7, can 'Enable UAC' task be changed/disabled?
I'd like to automate diabling UAC and keeping it disabled. We are running the K2000 version 3.7....the enable/disable UAc tasks are completely hidden from us to change or remove from a deployment.
Before anyone points me anywhere, Ive already read:
http://www.itninja.com/question/updated-to-3-6-can-new-tasks-be-changed-disabled
and
Explanation of the Disable/Enable UAC Tasks in 3.6 (121713) -- https://support.software.dell.com/kb/SOL121713
I have already created the task/post install bat script to set the value of the UAC.txt folder in such a manner that when the Restore UAC task runs, UAC will actually stay turned off. I also wrote a batch to replace the cleanup.vbs script (run as the very last task, also technically un-editable by a k2000 end user) with a modified copy that adds a reboot/placed in c:\kace during deployment...this all works fine, sort of Im not sure if the modified cleanup.vbs is actually being run/manually ran it and still have following issue. When the deployment is done, the UAC controls in the windows control panel still tell me that a reboot is needed to turn off UAC...a manual reboot does the trick. I dont want to manually reboot. We dont use a K1000 so I have no scripted reboots to kick off using it to accomplish this, nor do I want to go that route.
Getting to the question(s)...When can we expect to be able to remove and/or edit these hidden tasks or is there already an undocumented way? From what Ive read there is no way to gain write permissions to the \\kace\peinstall directories (which we be great for modifying these scripts so we can do things you havent thought of letting us do that we need to do...) So Is there a better way to permanently disable UAC that is not domain policy controlled or fully reversed by the running of the hidden UAC task? Or is there a better way to add a reboot task at the very end of a deployment, after the cleanup? Help appreciated...and I'll keep on trying to come up with my own workaround...
Before anyone points me anywhere, Ive already read:
http://www.itninja.com/question/updated-to-3-6-can-new-tasks-be-changed-disabled
and
Explanation of the Disable/Enable UAC Tasks in 3.6 (121713) -- https://support.software.dell.com/kb/SOL121713
I have already created the task/post install bat script to set the value of the UAC.txt folder in such a manner that when the Restore UAC task runs, UAC will actually stay turned off. I also wrote a batch to replace the cleanup.vbs script (run as the very last task, also technically un-editable by a k2000 end user) with a modified copy that adds a reboot/placed in c:\kace during deployment...this all works fine, sort of Im not sure if the modified cleanup.vbs is actually being run/manually ran it and still have following issue. When the deployment is done, the UAC controls in the windows control panel still tell me that a reboot is needed to turn off UAC...a manual reboot does the trick. I dont want to manually reboot. We dont use a K1000 so I have no scripted reboots to kick off using it to accomplish this, nor do I want to go that route.
Getting to the question(s)...When can we expect to be able to remove and/or edit these hidden tasks or is there already an undocumented way? From what Ive read there is no way to gain write permissions to the \\kace\peinstall directories (which we be great for modifying these scripts so we can do things you havent thought of letting us do that we need to do...) So Is there a better way to permanently disable UAC that is not domain policy controlled or fully reversed by the running of the hidden UAC task? Or is there a better way to add a reboot task at the very end of a deployment, after the cleanup? Help appreciated...and I'll keep on trying to come up with my own workaround...
3 Comments
[ + ] Show comments
-
Decided to leave UAC on, because off messes with some of our file associations/programs...going to apply the UAC never notify policy/reg hack...seem to be having trouble with that as Im applying it while UAC is off and can't apply it after its turned back on...suggestions? - ahuston@roguecc.edu 9 years ago
-
Solved I guess...Using my modified copy of cleanup.vbs to add reg keys as very last task if anyone is interested... - ahuston@roguecc.edu 9 years ago
-
I am glad your process led you to leaving UAC enabled. - Badger 9 years ago
Answers (1)
Please log in to answer
Posted by:
cserrins
9 years ago
So if I'm understanding this correctly, you captured an image with UAC enabled, but you want it disabled in the end. You used the uac.txt to make sure it stays disabled, but it requires a reboot in order to stay disabled.
If I have that right...
I could suggest creating a dummy .bat task, something that doesn't really do anything and tick the box for it to reboot. Make sure you increase the autologon count of course.
Corey
Corey
Lead T3 Enterprise Solutions Consultant, K2000
If I have that right...
I could suggest creating a dummy .bat task, something that doesn't really do anything and tick the box for it to reboot. Make sure you increase the autologon count of course.
Corey
Corey
Lead T3 Enterprise Solutions Consultant, K2000