Posted January 9, 201212 yr Hello all, I seemed to have run into some problems regarding my attempt to run Windows Easy Transfer when switching someone over from an XP box to a Windows 7 box. At first, everything seemed to go pretty well. There was one curiosity when the woman was not able to print from the previously configured network printer, but I just removed the old connection and reestablished it. This worked fine for several days until it crapped out again. The second time, though, I was not able to reconnect the printer and was constantly told that the print spool service was stopped under the one login (under my own everything was fine. . .I even attempted to make the user a local admin temporarily but there was no change for her under those conditions). The second problem that I encountered had to do with a pivot table speadsheet that uses a custom ODBC connection to draw updates from a database. Under the XP build, it seemed as if I can create the ODBC connection once and it would be picked up by the speadsheet as well as another application that uses the same databae. Under Windows 7, the connection was created and the application picked it up but not the spreadsheet. These problems were so noticable and high-profile (the user is the administrative assistant of the VP of Information Systems) that I needed to re-deploy the old XP box and now have to manually set up a user profile on the Windows 7 box. Another thing that I noticed after redeploying the XP box was that the ODBC connection was no longer there. Is it possible that sometimes WET corrupts a profile in the transfer, or that it actually removes things from the old profile as the process moves along? Has anyone else had similar types of problems when using WET? -Brian McKnight Continue reading...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.