![]() ![]() That procedure would need to be repeated for each and every limited user account that requred activation for the giveaway.ģ# this is more technical. The previously limited users account then downgraded to a limited user again before account is handed back to end user to play with. The Admin account owner needs to temporarily change the limited users accounts to Administrator accounts, the previously limited user can then login to their account or run as the Activate.exe from the Admins account using their credentials to activate the product in their account. #2 This requires someone with Admin rights to interviene which is kinda ok since limited users are not supposed to be installing programs anyway. ![]() That is the prefered solution and would solve the problem with no end user intervention. Where an activation is system wide because the reg file the vendor supplies is in the Local Machine HKLM registry hive then use this current Activate.exe with the built in manifest that instructs vista and above shells to insist it is given elevated Admin rights. This will NOT demand admin rights and will just work. There are a number of solutions rated in reverse preference.ġ# GAOTD team use the OLD Activate.exe when the reg file the vendor supplies is in the Current User HKCU registry hive and NOT in the HKLM ![]() #95, Phaedron: your point is 100% valid, it has happened because GAOTD team thought they'd solve the problem that SOMETIMES vista and above needs activate executed with Admin rights when the activation information is stored in a system wide location rather than in a per user account location, in reality they have made matters worse since Run-As changes the user profile to the As user used to get the Admin rights meaning the per-user activation activates the Admin account profile NOT the limited user accounts profile. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |