in for a penny, in for a pound. You may just want to go to PowerShell v2 to see if that resolves the whole thing. Although it got grouped in with the Windows Management Framework.
http://support.microsoft.com/kb/968929?wa=wsignin1.0 On Mon, Feb 11, 2013 at 5:47 AM, Andrew S. Baker <[email protected]> wrote: > Agreed. I've done several in-place 2008 x64 to 2008-R2 x64, and a couple > 2008 R2 to 2012, but those were on boxes I had completely controlled, so I > knew what to expect. > > In general, I would avoid doing that sort of upgrade, especially if lots > of software is installed. > > Why the upgrade? > > > > > > *ASB > **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker>* > **Providing Virtual CIO Services (IT Operations & Information Security) > for the SMB market…*** > > > > > > On Mon, Feb 11, 2013 at 8:07 AM, Webster <[email protected]> wrote: > >> Issues like these are why I never recommend in-place upgrades. Sorry >> that is no help to you now.**** >> >> ** ** >> >> Thanks**** >> >> ** ** >> >> ** ** >> >> Webster**** >> >> ** ** >> >> *From:* Rene de Haas [mailto:[email protected]] >> *Sent:* Sunday, February 10, 2013 5:17 PM >> *To:* NT System Admin Issues >> *Subject:* upgrading W2K3 to W2K8 both 32 bit, uninstalling Powershell >> breaks things.**** >> >> ** ** >> >> Hi,**** >> >> ** ** >> >> At the beginning of the upgrade it does a compatibility check and tells >> me to remove powershell.**** >> >> I check and it's version 1.0. When starting the uninstall it lists a >> whole bunch of stuff that will break if I uninstall it. Amongst other >> things the dot net framework, which breaks other programs. Also the >> programs they desperately need were mentioned. The program is using SQL >> server 2008 btw.**** >> >> ** ** >> >> I googled but didn't see anything indicating a way I can do this without >> uninstalling it.**** >> >> ** ** >> >> I uninstalled powershell. upgrade to W2K8 went fine.**** >> >> Program errored. Unfortunately, allmost nothing about the program is on >> the internet.**** >> >> Only on the manufacturers website. And that information leaves something >> to be desired.**** >> >> Added powershell 1.0 through features. Didn't fix the error.**** >> >> Repair dot net. Didn't fix it.**** >> >> ** ** >> >> In IIS I keep getting "The configuration section 'protocolMapping' >> cannot be read because it is missing a section declaration. The web.config >> file hasn't changed though.**** >> >> ** ** >> >> Maybe I could start over, change the powershell registry key a bit and >> after the upgrade restore it?**** >> >> ** ** >> >> Grateful for any ideas**** >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> >> --- >> To manage subscriptions click here: >> http://lyris.sunbelt-software.com/read/my_forums/ >> or send an email to [email protected] >> with the body: unsubscribe ntsysadmin >> >> > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
