The first time I installed EVERYTHING, I cheated a little bit and did some updates in the background while I worked. Maybe you IT guys and Managers can pick out something useful.įirst Mistake Not allowing all the Vista updates to get settled before installing components. I’ll go through some of the key things that did and did not work. All I know is the items in the en-us folder were missing, and she wouldn’t run. It’s hard to say exactly because no one can sit there and stare at the 1.5 hour install. The long and short is that the install would blue screen right about when it would shift over to the Language Pack, every time. This week I have installed Vista + updates twice, Civil 3D 2009/2010 twice, Inventor 2009 once, Inventor 2010 5 times, Vault server twice, AV and authoring software suites twice as well.Īs of last night, Inventor 2010 would not work (properly). How many of you are laughing now? At 8, I was not laughing. I‘ll come in at 4 am, and by 8 we’ll be functional”. I kept thinking, “we have this down to a science, no problem. Any engineering OS older than 6 months is gravy. I’ve got a bright idea, ‘lets reinstall Vista’. I blue screened, and everything seemed to operate fine afterward, but the licensing component started freaking out, and eventually would not let me into Autodesk products.
Now we have a sonic wall and keeps me pretty clean. I push the limit with space and implementing new things, so my OS gets flaky sometimes.
Microsoft recommends that the policy be set back to 0 upon completion of the install maintenance. The Installer key does not exist by default on Windows 7, but is safe to add.įor more information about this Windows Installer policy, see: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft
0 kommentar(er)
