Windows 2008 Upgrade Paths, and the Problem with Exchange 2007


Ask The Performance Team has a blog posting on the upgrade paths for Windows 2008, which is set to be released at the end of this month. To begin, lets get two things clarified right away. There is no way to perform cross-platform upgrades, i.e. x86 to x64 architecture, and there is no way to upgrade from a previous version of Windows to Windows 2008 Server Core Edition. If you’re unfamiliar with Server Core, it’s installation provides a minimal environment for running specific server roles that reduces the maintenance and management requirements and the attack surface for those server roles.

Available upgrade paths from Windows Server 2003 to Windows Server 2008 are:

  • If you are currently running Windows Server 2003 Standard Edition (R2, SP1 or SP2), you can upgrade to the full installation of Windows Server 2008 Standard Edition or the full installation of Windows Server 2008 Enterprise Edition.
  • If you are currently running Windows Server 2003 Enterprise Edition (R2, SP1 or SP2), you can upgrade to the full installation of Windows Server 2008 Enterprise Edition.
  • If you are currently running W indows Server 2003 Datacenter Edition (R2, SP1 or SP2), you can upgrade to the full installation of Windows Server 2008 Datacenter Edition.

Also note that you must test all applications before migrating to any version of Windows Server 2008. Read all about the Exchange Team’s effort to migrate Exchange 2007 from Windows 2003 to Windows 2008; all of the caveats and requirements can make your head hurt.

The big problem ends up being:

Exchange 2007 SP1 can be installed on Windows Server 2008, but Windows Server 2008 cannot be installed on Exchange 2007 SP1. This means that all computers running Exchange 2007 SP1 must have Windows Server 2008 already installed before Exchange can be installed on the system. This also means that you cannot take an existing Exchange 2007 server (RTM or SP1) running on Windows Server 2003, and do an in-place upgrade of the operating system to Windows Server 2008.

Put another way:

When upgrading standalone servers, it is not supported to upgrade your operating system to Windows Server 2008 and then upgrade Exchange 2007 to SP1. It is also not supported to upgrade Exchange 2007 to SP1 and then upgrade your operating system to Windows Server 2008. To deploy Exchange 2007 SP1 on Windows Server 2008, you must install Windows Server 2008 on a computer that does not have Exchange installed, and then install Exchange 2007 SP1.

To help assist IT professionals with determining if their existing networking environment will support Windows Server 2008, Microsoft has developed the Microsoft Assessment and Planning (MAP) Solution Accelerator, which is now available for download. You can read more about this tool at the MAP Team blog.

The Microsoft Assessment and Planning Solution Accelerator performs three key functions, including hardware and device inventory, compatibility analysis, and readiness reporting. The Microsoft Assessment and Planning tool is based on agentless infrastructure scanning technology that makes it easier to set up the inventory without the requirement of installing any software agents on each machine being inventoried.

(MAP) is the expanded version of the Windows Vista Hardware Assessment solution accelerator (WVHA). This new version of the network-wide assessment tool gives you not only the original capability of hardware inventory and assessment for desktops, but also expanded features including server migration recommendation with Windows Server 2008, virtualization workload placements for server consolidation with Hyper-V or Virtual Server 2005 R2, and application virtualization recommendations with Microsoft Application Virtualization.

1607: Unable to install Installshield Scripting Runtime during Groupwise client install


I was trying to install the Groupwise 7.0.1 client on a Windows 2000 machine that was running the Groupwise 6.5.7 client, and kept getting the following error:

1607: Unable to install Installshield Scripting Runtime

I tried uninstalling the Groupwise 6.5.7 client, rebooting, then running the client 7.0.1 setup again, but it didn’t make any difference.

I tried the suggestions in Q107070 from support.installshield.com, still couldn’t install the client.

I updated the Windows Install to version 3.1 (KB893803) per Q108201 – it made no difference, I still received the 1607 error.

I Uninstalled Windows Installer 3.1, rebooted the PC, renamed the C:\Program Files\Common Files\Installshield directory, then ran Windows Installer 3.1 setup again, and was finally able to install Groupwise 7.0.1 client.

Just to note, Novell recommends you should update your entire Groupwise environment to 7.0.2 Hot Patch 1a as soon as possible, since security issues have been discovered with version 7.0.1.

Howto: Upgrade OES iManager 2.5 to iManager 2.6 SP3 (and fix some nici problems as well)


Novell’s iManager hasn’t worked for me since I freshly installed my Novell Open Enterprise Server (OES) SP2 linux server. When I access http://myserversip/nps (or https://10.0.0.26/iManager.html), I’m presented with the iManager login screen, but when I enter my credentials I receive the following error:

Server Error 500

Either the server is overloaded or there was an error in a CGI script

Most articles and posts I read pointed to tomcat as the culprit. iManager 2.5 has had several security issues, so the recommended action is to upgrade to 2.6, which I had planned on doing some day… just not today.

I didn’t find much information regarding upgrading from iManager 2.5 to 2.6 on OES Linux, so I just decided to wing it , and had to perform a lot of trial and error troubleshooting during the process.

This is how I performed the upgrade:

1) From the Novell Download site, download the version of iManager 2.6 appropriate for your operating system (I selected the Linux version for OES). You will have to login to Novell in order to access the files, if you don’t have a Novell account you can get one here.

2) Change to the directory you saved the iManager file download in. Extract the files using the following syntax: (note it is case sensitive)

tar -zxvf iMan_26_linux.tgz

3) change to the directory where the binary file is located using the following syntax:

cd /iManager/installs/linux

4) To being the setup program, type:

./iManagerInstallLinux.bin

(you can get more detailed information on installing iManager 2.6 here)

5) Select 2 to install in English or select your language of choice

6) Press enter several times, then Y to accept the license agreement

7) Press enter to accept all the default installation options. I would only change these if you really know what you’re doing.

8) Sit back and prepare to wait a while. On my brand new Dell PowerEdge 2950 with 4GB of RAM the install took about 20 minutes. After the install has completed, I suggest you reboot, then verify iManager 2.6 is accessible (default login page is https://yourserverip/nps/iManager.html), but it’s your call. I’m glad I tried, because when I tried to authenticate I received the following error:

Unable to initialize JClient: java.lang.Error: Unable to initialize DClient

TID 10100826 explains the problem has to do with NICI, which doesn’t play nice with Tomcat and makes it so you can’t login any more. This TID says to rename the /var/novell/nici/101 directory and restart tomcat to fix this issue, but I don’t have a 101 directory in /var/novell/nici. I thought maybe the 101 was maybe a subdirectory of some other nici directory, so I searched and found the serveer did have the following nici directories:

/var/opt/novell/nici – contained 8 files and 1 folder named ’0′ (thats a zero, not a small o)

/opt/novell/oes-install/nici – directory was empty

/opt/novell/oes_install/nici – only contained a ########.nfk file, which is a license file.

So I went ahead and renamed the /var/opt/novell/nici/0 folder to 0.old and restarted tomcat with the following command:

rctomcat restart

I tried to login to iManager again, and I received the same Jclient error shown above.

TID 10077278 said to edit the environment variable found in the tomcat.sh file, but I couldn’t find a tomcat.sh file on my server (tomcat run just fine, incidently).

I found this post that sets up nici in server rather than client mode. To fix nici, I did:

1) Renamed the /var/opt/novell/nicifk file.

2) Copied my ########.nkf file from /opt/novell/oes_install/nici to the /var/opt/novell directory

3) Renamed my ########.nkf file from step 2 nicifk

4) Assigned the same rights to the new nicifk file that the old nicifk file had, which were -r-xr-xr-x. To do this, I typed:

chmod 555 nicifk

5) From the /var/opt/novell/ directory I tried to regenerate the ’0′ directory by running primenici, but I received the following error:

Initializing NICI… sh: line 1: /var/novell/nici/nicimud: No such file or directory

failed, error -1497

To fix the error -1497, I found this post which talks about creating soft links to nici folders because of an eDirectory 8.8 upgrade (which we don’t use, all servers are still on eDir 8.7.3). To fix this particular nici error, I typed:

ln -sf /var/opt/novell/nici /var/novell/nici

/var/opt/novell/nici/set_server_mode

/var/opt/novell/nici/primenici

and the ’0′ directory was recreated for me! I felt like I was finally getting somewhere!

To restart tomcat, I typed:

rctomcat restart

then tried to login to iManager again, but to my dismay, still experienced the Jclient/Dclient error.

So I rebooted the server and went to get some lunch. When I tried to access iManager again, I received a different error:

NDS Error -626

(Error -626) The object could not be found. It is possible that the object exists, but the server could not communicate with the server holding a copy of the object.

This error sounded like it could be fixed by adding a replica to the OES server, and since I was planning on doing it eventually anyway, I used ConsoleOne to create a read only replica.

I waited for the Current Sync Error condition to change to No Error in C1′s replica information screen, then restarted tomcat. I held my breath as I attempted to login to iManager 2.6 (no SP), and it worked! I rebooted the server once again just to make sure it was really working, and once again I logged in without problems!
**********

Once your iManager has been upgraded from 2.5 to 2.6, we can apply iManager 2.6 SP3, which is the most recent update as of June 27, 2007. Go download iManager Support Pack 3. Once again, you have to login to your Novell account to get this update.

To decompress the support pack, type:

tar -zxvf iman26sp3.tgz

Follow these directions to install iManager SP3. Please note, you need to have this support pack installed to have support for the Internet Explorer 7 and Firefox 2.0 browsers, so for be results, do the installation from IE6 or Firefox 1.5.x.

Don’t forget to restart tomcat after you complete the update to SP3. I suggest restarting the entire server if you can get away with it.

eDirectory 8.8 / 8.8.1 and nw65sp6


According to the readme file included with Netware 6.5 Service Pack 6 (Last modified: 06Nov2006),

“If you have eDirectory 8.8 installed on the server, copy the dhost.nlm (dated 18Sep2006 09:36AM) to the server’s sys:\system directory and reboot the server before applying the Support Pack. “

Then the Novell eDirectory 8.8 Readme Addendum was released and has become a living document listing the known issues with eDirectory 8.8.

okay…

then Novell released eDirectory 8.8.1, which they had security problems. To fix this issue, they released eDirectory Post 8.8 SP1 FTF1 for NW & Win32 which is a patch for the compromised eDirectory 8.8.1 support pack. This TID states:

“NOTE: This patch contains a new DHOST.NLM (dated 10-16-2006 05:29pm) that must be installed on a NetWare 6.5 server running eDirectory 8.8.1 prior to installing Support Pack 6.”

Which is fine and dandy, except here came Security Services 2.0.4, which notes:

“If you install NetWare 6.5 SP6 and upgrade to eDirectory 8.8 or eDirectory 8.8 SP1, the eDirectory install will backrev NMAS, PKIS and NICI. If this happens, applying this patch is appropriate.”

and

“If you are installing the Security Services 2.0.4 patch on a NetWare 6.5 server with eDirectory 8.8 SP1 installed, you MUST apply “eDirectory Post 8.8 SP1 FTF1″ for NetWare (or greater) prior to applying the Security Services 2.0.4 patch or the install will hang. If you did not apply the “eDirectory Post 8.8 SP1 FTF1″ (or greater) patch before installing the Security Services 2.0.4 patch and the installation hangs, apply the above patch and rerun the Security Services 2.0.4 install.”

Continuing the saga, then came eDirectory Post 8.8 SP1 FTF2, which stated:

“This is being provided to resolve known security issues as well as critical defects. NOTE: This patch contains a new DHOST.NLM (dated 2007-01-25 10:09:46) that must be installed on a NetWare 6.5 server running eDirectory 8.8.1 prior to installing Support Pack 6.”

If you’re feeling truely adventurous, you can try migrating to eDirectory 8.8 SP2 once it’s released, but I suggest performing a migration dry run before doing the real thing.

Since I have Netware 6.5 and eDirectory 8.8.x, before I update my servers, I’m going to:

1) Carefully read the readme file for NW65SP6 before doing anything.

2) Search the Novell support knowledge base for updated TIDs on eDirectory 8.1.x and Netware 6.5 SP6.

2) Determine the version of eDirectory I have on each server prior to applying Netware 6.5 Service Pack 6. To do this, on the system console type version

3) Apply the appropriate patches, reboot, and run a dsrepair on the master just to be safe once eDirectory has been patched. TID 3426981 appears to be a living document that keeps up with all the changes in the eDirectory updates.

4) Backup eDirectory using dsbk before attempting any patching or upgrades

Windows 2003 SP2 problems on Windows 2003 SBS servers


When new service packs are released by Microsoft, I tend to wait a few weeks before installing them on my systems. Why? I’ve been burned before by ‘updates’ that make systems unstable, unusable, or even unbootable.

It’s awful nice of Microsoft to finally release a KB article describing the problems Windows 2003 SP2 can cause on Windows 2003 Small Business Servers. I mean, it was only released on March 13, 2007.

Before you install this service pack on a SBS 2003 server, read the official release notes. Then, read Susan Bradley’s unofficial release notes, which detail the proper way to apply the update. Update your NIC drivers, especially for Broadcom NICs prior to installation.

[update June 1, 2007]

According to Susan, both HP and Dell have announced firmware updates for their Broadcom NICs.

[update June 14, 2007]

Susan has detailed notes available that describe the entire process for installing Windows 2003 SP2

Follow

Get every new post delivered to your Inbox.

Join 32 other followers