I
IT@C
Hello,
we have been struggling for a while now with the update to Windows 2003
Server Service Pack 2.
When installed on every server in our environment we encounter problems.
Uninstalling usually fixes the issue but not always.
I will list the problems and our network.
1. Network running Windows 2003 Server SP1 on 5 servers, (4 x DC, one member
server)
2. Exchange Server 2003 is on four servers, 3 x BE and 1 x FE
3. AD used
4. Windows 2003 Server stand-alone server, in its own workgroup
Issue 1.
On Exchange Front End server (member server)
- After Windows 2003 Server SP2 installed (via WSUS) we were no longer able
to log into OWA, although we received the login prompt
- Uninstall of Windows server SP2 fixed the problem
Issue 2.
on one DC, running Exchange 2003 server
After Windows 2003 Server SP2 was installed via WSUS
- New users created with a roaming profile receive an error stating that
their roaming profile was not accessible and that teh local profile was also
not accessable, and a TEMP profile was used.
- Our setup was no different from normal, all users are set up with roaming
profiles and prior to SP2 users would never see any errors.
We have not removed SP2 yet as we are concerned this will cause further
damage.
Issue 3.
Stand-alone server in its own workgroup
- We installed Windows 2003 Server R2
-We installed Terminal Services and terminal Services licensing on this server
- Windows 2003 Server SP2 was applied via Windows Update not WSUS
-We attempted to install IIS from the R2 CD. IIS never completed the
install. Was this becuase we used a pre-SP2 CD?
-The Terminal Services Licensing server previously installed on this same
server could no longer be found.
- Uninstalled SP2, TS licensing server was found on restart but not on
subsequent restarts
- We re-installed windows 2003 Server R2, with IIS and TS licensing and TS
manager but WITHOUT SP2 and all applications worked.
We are loathe to attempt any further SP2 installs, especially in light of
issues 1 and 2, although issue 3 was also frustrating.
SP2 was installed via Windows update
Any assistance or pointers would be appreciated.
IT@C
we have been struggling for a while now with the update to Windows 2003
Server Service Pack 2.
When installed on every server in our environment we encounter problems.
Uninstalling usually fixes the issue but not always.
I will list the problems and our network.
1. Network running Windows 2003 Server SP1 on 5 servers, (4 x DC, one member
server)
2. Exchange Server 2003 is on four servers, 3 x BE and 1 x FE
3. AD used
4. Windows 2003 Server stand-alone server, in its own workgroup
Issue 1.
On Exchange Front End server (member server)
- After Windows 2003 Server SP2 installed (via WSUS) we were no longer able
to log into OWA, although we received the login prompt
- Uninstall of Windows server SP2 fixed the problem
Issue 2.
on one DC, running Exchange 2003 server
After Windows 2003 Server SP2 was installed via WSUS
- New users created with a roaming profile receive an error stating that
their roaming profile was not accessible and that teh local profile was also
not accessable, and a TEMP profile was used.
- Our setup was no different from normal, all users are set up with roaming
profiles and prior to SP2 users would never see any errors.
We have not removed SP2 yet as we are concerned this will cause further
damage.
Issue 3.
Stand-alone server in its own workgroup
- We installed Windows 2003 Server R2
-We installed Terminal Services and terminal Services licensing on this server
- Windows 2003 Server SP2 was applied via Windows Update not WSUS
-We attempted to install IIS from the R2 CD. IIS never completed the
install. Was this becuase we used a pre-SP2 CD?
-The Terminal Services Licensing server previously installed on this same
server could no longer be found.
- Uninstalled SP2, TS licensing server was found on restart but not on
subsequent restarts
- We re-installed windows 2003 Server R2, with IIS and TS licensing and TS
manager but WITHOUT SP2 and all applications worked.
We are loathe to attempt any further SP2 installs, especially in light of
issues 1 and 2, although issue 3 was also frustrating.
SP2 was installed via Windows update
Any assistance or pointers would be appreciated.
IT@C