/build/static/layout/Breadcrumb_cap_w.png

Progress and Problems with XP Migration

I have two domains....ROOT.PRV being my main domain, and CMONEY.PRV being my test Domain. Both Domains Run Win2k Server
In ROOT. I ran a VMWARE Image of WinXP on a Win2k Machine. Added the WinXP machine to the ROOT domain, and was able to deploy software from Root to the Virtual XP machine, and almost all of my Win2k Packages worked in the XP environment!!!

Next level of testing on CMONEY.PRV I moved over a few win2k Packages. Set up the same permissions and GP on CMONEY as I have on ROOT.PRV and attempted to deploy software to a physical test machine running XP. The software will not deploy. First assumtion is that I had a group policy or an OU or some other setting or path incorrect. I checked them, they all APPEAR fine. So I try to deploy again, and again no such luck. Ok....next step, I hook a workstation running win2k up to CMONEY deploy software fine.

Anyone has any ideas why in the first test environment it worked. In the second one it will not deploy to winXP but will deploy to win 2k.

0 Comments   [ + ] Show comments

Answers (6)

Posted by: Rhys 17 years ago
Orange Belt
0
What are you using to deploy the software? AD, SMS, something else? If it's SMS, I'd check under the programs requirements and make sure that XP is an allowed OS.
Posted by: Stinger 17 years ago
Senior Yellow Belt
0
deploying the software using AD
Posted by: Rhys 17 years ago
Orange Belt
0
Sorry, I'm not familar with AD distribution. Hopefully someone else can help you out.
Posted by: nheim 17 years ago
10th Degree Black Belt
0
Hi Stinger,
what does the Event Viewer (Application-Tree) tell you on the XP Clients?
Usually, there is quite usefull logging info in there.
Regards, Nick
Posted by: AngelD 17 years ago
Red Belt
0
Run rsop.msc to verify that the GPO is applied to the xp clients.
Posted by: trent 17 years ago
Yellow Belt
0
A bit late on this one as ive only just joined.
Silly question, but do you have the Group Policy Object: Computer Configuration>Administrative Templates>System>Logon> "Always wait for network connection at computer startup and logon" set to enable?
This is off by default and as AD deployed apps happen at startup and require a network connection this needs to be enabled.
Depending on the circumtances of your app deployment this can be set at the Domain or Local GPO
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ