RapidInstall changes the XP Activation
Hi all,
We are using RapidInstall to deploy small updates. We make the package on a Windows XP SP2 with a Volume License nut when deploying on other computers they have to activate Windows after a restart. I suppose that there something in the registry that RapidInstall captures that should not be captured.
Anyone has an idee what registry entries could cause this? (I can post the registry changes but they are long)
Best Regards
Martin
We are using RapidInstall to deploy small updates. We make the package on a Windows XP SP2 with a Volume License nut when deploying on other computers they have to activate Windows after a restart. I suppose that there something in the registry that RapidInstall captures that should not be captured.
Anyone has an idee what registry entries could cause this? (I can post the registry changes but they are long)
Best Regards
Martin
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
crawl
17 years ago
Hi Maeron,
Right off the top of my head, I don't know which key would be but I have an .ini file that has been built up over the years using Wise Package Studio that is full of registry exclusions. I used to use RapidInstall also but just ran into way too many problems so our organization purchased Wise Package Studio which has made a huge difference. Anyway, I will e-mail you the .ini file. Hopefully it will be helpful to you.
James
Right off the top of my head, I don't know which key would be but I have an .ini file that has been built up over the years using Wise Package Studio that is full of registry exclusions. I used to use RapidInstall also but just ran into way too many problems so our organization purchased Wise Package Studio which has made a huge difference. Anyway, I will e-mail you the .ini file. Hopefully it will be helpful to you.
James
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
