In attempting to install VMware vSphere PowerCLI on Windows Server 2008 x64, the following error comes up. This also happens on Server 2008R2.
Error 1406. Could not write value InstallPath to key \Software\VMware, Inc.\VMware vSphere PSDK Runtime. Verify tha tyou have sufficient access to that key, or contact your support personnel.
The prescribed fix for this is to remove the following registry key (and subkeys):
HKLM\Software\Wow6432Node\VMware, Inc.
*** Please make sure you know what you are doing in the registry before you do anything in there!!!
After that, installation proceeds successfully.
The only thing under the VMware, Inc. registry key is a "volatile" key with a UUIDHost DWord under it. Since I don't like to mess with other programs installed on the server (the one I was using has Quest vRanger installed), I exported the key, removed it, installed PowerCLI, and the imported my volatile key back in.
------
Dustin Shaw
VCP
Notes on server implementations and fixes for VMware, Microsoft, and other fun projects.
Showing posts with label 2008. Show all posts
Showing posts with label 2008. Show all posts
Tuesday, February 21, 2012
Monday, December 13, 2010
Exchange 2010 Prereq Script
I was looking for an easy way to install all the Prerequisites on a new Exchange 2010 install this last week, and ran across a good script that does it all for you.
The script was written by Dejan Foro over at ExchangeMaster.net. You can find it here.
He has several variations of the script: one that lets you choose what server roles you are installing, or one that installs all prerequisites needed if you are loading down a box with all Exchange Roles.
It's also got variations for whether you are running Server 2008 SP2 or Server 2008 R2.
It's available in either ISO or ZIP format.
------
Dustin Shaw
VCP
The script was written by Dejan Foro over at ExchangeMaster.net. You can find it here.
He has several variations of the script: one that lets you choose what server roles you are installing, or one that installs all prerequisites needed if you are loading down a box with all Exchange Roles.
It's also got variations for whether you are running Server 2008 SP2 or Server 2008 R2.
It's available in either ISO or ZIP format.
------
Dustin Shaw
VCP
Monday, October 18, 2010
Entourage 2008 connection issues to SBS 2008
Most things with Small Business Server 2008 work out of the box. Some do not.
Here's one that doesn't - Entourage 2008 connection from outside the network. Outlook uses RPC over HTTPS and works great. Entourage uses WebDAV and it doesn't. It usually works fine with most Exchange 2007 setups (as long as they are configured properly), but it doesn't with the custom config known as SBS 2008.
The solution is to allow the "Authenticated Users" Group to have "Read and Execute", "List Folder Contents", and "Read" access to the following folders:
C:\Program Files\Microsoft\Exchange Server\ClientAccess
C:\Program Files\Microsoft\Exchange Server\ClientAccess\Exchweb
C:\Program Files\Microsoft\Exchange Server\ClientAccess\OWA
And then you need to make sure you are connecting to the exchange server using the following format:
remote.domain.com/exchange/username@domain.com
And then you should be good to go.
That is of course if you are up to date on your Exchange 2007 SP2 or higher. If not, then it will probably break the RPC over HTTPS so that it continually prompts for username and password and never connects. The solution for this is either update to Exchange 2007 SP2 or do the following:
Go to IIS (7)
Go to Sites -> SBS Web Applications
In the following Virtual Directories, change the SSL settings to Accept Client Certificates:
OAB
RPC
RPCWithCert
I've seen some people that also recommend you should do the Autodiscover Virtual Directory, but I've not seen this needed.
------
Dustin Shaw
VCP
Here's one that doesn't - Entourage 2008 connection from outside the network. Outlook uses RPC over HTTPS and works great. Entourage uses WebDAV and it doesn't. It usually works fine with most Exchange 2007 setups (as long as they are configured properly), but it doesn't with the custom config known as SBS 2008.
The solution is to allow the "Authenticated Users" Group to have "Read and Execute", "List Folder Contents", and "Read" access to the following folders:
C:\Program Files\Microsoft\Exchange Server\ClientAccess
C:\Program Files\Microsoft\Exchange Server\ClientAccess\Exchweb
C:\Program Files\Microsoft\Exchange Server\ClientAccess\OWA
And then you need to make sure you are connecting to the exchange server using the following format:
remote.domain.com/exchange/username@domain.com
And then you should be good to go.
That is of course if you are up to date on your Exchange 2007 SP2 or higher. If not, then it will probably break the RPC over HTTPS so that it continually prompts for username and password and never connects. The solution for this is either update to Exchange 2007 SP2 or do the following:
Go to IIS (7)
Go to Sites -> SBS Web Applications
In the following Virtual Directories, change the SSL settings to Accept Client Certificates:
OAB
RPC
RPCWithCert
I've seen some people that also recommend you should do the Autodiscover Virtual Directory, but I've not seen this needed.
------
Dustin Shaw
VCP
Tuesday, September 7, 2010
Disabling IPv6 on Server 2008/2008r2
As an outsource IT professional, there is one thing that I've run into over and over again in SMBs - IPv6 doesn't play well unless FULLY integrated. That means if you try to simply "uncheck" the box for IPv6 to disable it, you've just hosed yourself. Similarly, if you just left it checked because you don't know what your doing, you've just hosed yourself.
There are a number of issues that I've seen because of the idiocracy above:
- Slow XP performance on every task when joined to a domain with a 2008 server with IPv6
- Broken SBS 2008 server when you uncheck the box (things that break are "Applying Computer Settings" for a long time, Exchange won't start, Network Icon shows offline in error)
- Exchange 2010 won't install when IPv6 is unchecked (but not disabled)
- Exchange 2007 and Exchange 2010 won't start when unchecked (but not disabled)
- Other "random" issues that can't be pinned down
So basically you have two solutions:
Since I'm betting that most people like to go the way of "cheap," I'll detail that one for you :-) If you'd rather go balls-to-the-walls, go for it. Just make sure you understand the animal first.
--
On your new, shiney Server 2008 / 2008r2, first you want to Uncheck the box that says "IPv6" (DUHH!)
Once that's done, go to Regedit***. You'll want to navigate here:
HKEY_Local_Machine\System\CurrentControlSet\Services\Tcpip6\Parameters
Create a DWord (32-bit) value named "DisabledComponents" and Click OK. Note: There is no space in the DWord name - and no quotes either ;-)
Double Click you're new "DisabledComponents" DWord and put in the following value to completely disable ALL of IPv6 (except IPv6 loopback interface):
ffffffff --- Hex
or
4294967295 --- Dec
Click OK.
There are also other options to do with this DWord, as detailed perfectly by MS here:
http://support.microsoft.com/kb/929852
Once done, restart your server to make sure that everything takes full effect. I've seen it take effect without restart, but restart is always best practice when playing with the registry.
If you have additional servers running 2008 or 2008r2: rinse, lather, repeat.
Now you should have smooth sailing with just IPv4 on the network. And if it's not smooth, at least you know that IPv6 wasn't your problem :-)
------
Dustin Shaw
VCP
~~~~***~~~~
Danger! Danger!
Don't go playing with the registry unless you actually know what you're doing.
If you don't know what you're doing in the registry, bad bad things ensue.
If you insist on playing in the registry anyway, you should also go update your resume and notify your boss that they will soon need a replacement that can rebuild a server.
Danger! Danger!
~~~~***~~~~
Here's some books that should help out:
IPv6 Essentials
Understanding IPv6, Second Edition
There are a number of issues that I've seen because of the idiocracy above:
- Slow XP performance on every task when joined to a domain with a 2008 server with IPv6
- Broken SBS 2008 server when you uncheck the box (things that break are "Applying Computer Settings" for a long time, Exchange won't start, Network Icon shows offline in error)
- Exchange 2010 won't install when IPv6 is unchecked (but not disabled)
- Exchange 2007 and Exchange 2010 won't start when unchecked (but not disabled)
- Other "random" issues that can't be pinned down
So basically you have two solutions:
- Implement IPv6 on EVERYTHING - aka get a new switch, router, firewall, etc. that supports IPv6, configure it and everything else with IPv6 (that includes any legacy XP or 2003 boxes in the network), and get it all working. Then you just translate to the IPv4 world for the rest of your internet until everyone jumps on that bandwagon. Oh, and by the way, you'll probably need to replace all your gear before it gets to that point.
- Go the cheap route and completely disable IPv6. I say cheap because it's not only cheaper in hardware (you don't have to replace all your infrastructure just because of IPv6 compatibility - granted, it can give you a good bullet point to show the boss if you want to anyway...), but it's cheaper in labor because you don't have to teach all your geeks (umm, I mean IT professionals...) how to read and understand the new subnets.
Since I'm betting that most people like to go the way of "cheap," I'll detail that one for you :-) If you'd rather go balls-to-the-walls, go for it. Just make sure you understand the animal first.
--
On your new, shiney Server 2008 / 2008r2, first you want to Uncheck the box that says "IPv6" (DUHH!)
Once that's done, go to Regedit***. You'll want to navigate here:
HKEY_Local_Machine\System\CurrentControlSet\Services\Tcpip6\Parameters
Create a DWord (32-bit) value named "DisabledComponents" and Click OK. Note: There is no space in the DWord name - and no quotes either ;-)
Double Click you're new "DisabledComponents" DWord and put in the following value to completely disable ALL of IPv6 (except IPv6 loopback interface):
ffffffff --- Hex
or
4294967295 --- Dec
Click OK.
There are also other options to do with this DWord, as detailed perfectly by MS here:
http://support.microsoft.com/kb/929852
Once done, restart your server to make sure that everything takes full effect. I've seen it take effect without restart, but restart is always best practice when playing with the registry.
If you have additional servers running 2008 or 2008r2: rinse, lather, repeat.
Now you should have smooth sailing with just IPv4 on the network. And if it's not smooth, at least you know that IPv6 wasn't your problem :-)
------
Dustin Shaw
VCP
~~~~***~~~~
Danger! Danger!
Don't go playing with the registry unless you actually know what you're doing.
If you don't know what you're doing in the registry, bad bad things ensue.
If you insist on playing in the registry anyway, you should also go update your resume and notify your boss that they will soon need a replacement that can rebuild a server.
Danger! Danger!
~~~~***~~~~
Here's some books that should help out:
IPv6 Essentials
Understanding IPv6, Second Edition
Subscribe to:
Posts (Atom)