W2K3 SP2 on SBS 2003 Premium

I installed W2K3 SP2 on a SBS Premium. This particulate server is running an
FTP site for thin clients. Information about the FTP site is passed to the
thin clients by DHCP server. Thin Client could not access the FTP site after
the installation. We could not find any reasonable explanation. This was
preventing 120 users in a 40 device network from doing their job. We also
noticed a slowdown of the network and had problems accessing the terminal
server (slow logon) trough RDP on PCs. We therefore had to uninstall W2K3
SP2. A server restart and the problem was resolved. Anny suggestions?

It appears that you're not the only one to have seen a DHCP issue after
installing Windows Server SP2 on SBS Premium. Since you've already removed
the SP and that's apparently solved your immediate problem, I'd wait to
reinstall it until we get more information about this. If it turns out that
this is any kind of trend, there'll be more info shortly.


"Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
message news:F6804D0F-D486-4DA4-9E54-AECF49656607@microsoft.com...
>I installed W2K3 SP2 on a SBS Premium. This particulate server is running
>an
> FTP site for thin clients. Information about the FTP site is passed to the
> thin clients by DHCP server. Thin Client could not access the FTP site
> after
> the installation. We could not find any reasonable explanation. This was
> preventing 120 users in a 40 device network from doing their job. We also
> noticed a slowdown of the network and had problems accessing the terminal
> server (slow logon) trough RDP on PCs. We therefore had to uninstall W2K3
> SP2. A server restart and the problem was resolved. Anny suggestions?

What I have come to realize, is that this SBS Server is a R1, CD for R2 has
arrived but it has not been installed. In requirement “R2” is used. This may
or may not be related. But way did it then appear in Microsoft Update if it
should not be applied? I chose to install after testing on a virtual server,
there after may Action Pack installation. No problem so far whit those. The
DHCP was delivering IPs, I did not have the time to test to investigate what
was actually wrong. Employees where leaving work! I had to get the server
up. On this particular server I am using Scope Option 161 and 162. I will
take our advise, and thank you for your answer!

The WS03 SP does not require R2. But, there does appear to be some issue
with certain Premium users installing it. Hopefully more info will be
coming soon.

This is a good opportunity for me to point out that it's a good idea for
people who have issues with service packs to call PSS (Microsoft Support).
Service pack support is free, and while you would not want to abuse that,
this type of issue is good to call on - more than one person seeing it, and
uninstalling the SP fixes it - they need to know that.

"Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
message news:6DB219D9-877F-4FBE-9445-AB5554313EF3@microsoft.com...
> What I have come to realize, is that this SBS Server is a R1, CD for R2
> has
> arrived but it has not been installed. In requirement "R2" is used. This
> may
> or may not be related. But way did it then appear in Microsoft Update if
> it
> should not be applied? I chose to install after testing on a virtual
> server,
> there after may Action Pack installation. No problem so far whit those.
> The
> DHCP was delivering IPs, I did not have the time to test to investigate
> what
> was actually wrong. Employees where leaving work! I had to get the server
> up. On this particular server I am using Scope Option 161 and 162. I will
> take our advise, and thank you for your answer!

I haven’t realized this! I will call PSS.
By the way, I have a SBS Standard R1 upgraded to R2 standard, upgraded to R2
Premium where ISA Server 2004 will not install. It is interrupted because it
can not install MSDE. I have googled log errors and tested 2 MVP workarounds.
I am able to complete a sort of install. Thereafter I am running the SBS
install “script” on the CD. ISA is then configured for SBS. When done, there
seems to be some sort of a RPC issue. I therefore had to uninstall. Is this
type of issue also PSS covered on PSS? I am currently about to use one of may
TechNet support cases?


"Dave Nickason [SBS-MVP]" wrote:

> The WS03 SP does not require R2. But, there does appear to be some issue
> with certain Premium users installing it. Hopefully more info will be
> coming soon.
>
> This is a good opportunity for me to point out that it's a good idea for
> people who have issues with service packs to call PSS (Microsoft Support).
> Service pack support is free, and while you would not want to abuse that,
> this type of issue is good to call on - more than one person seeing it, and
> uninstalling the SP fixes it - they need to know that.
>
> "Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
> message news:6DB219D9-877F-4FBE-9445-AB5554313EF3@microsoft.com...
> > What I have come to realize, is that this SBS Server is a R1, CD for R2
> > has
> > arrived but it has not been installed. In requirement "R2" is used. This
> > may
> > or may not be related. But way did it then appear in Microsoft Update if
> > it
> > should not be applied? I chose to install after testing on a virtual
> > server,
> > there after may Action Pack installation. No problem so far whit those.
> > The
> > DHCP was delivering IPs, I did not have the time to test to investigate
> > what
> > was actually wrong. Employees where leaving work! I had to get the server
> > up. On this particular server I am using Scope Option 161 and 162. I will
> > take our advise, and thank you for your answer!
>
>
>

In reference to the SP2 install on SBS 2003 Premium, The problem I
experienced is the disappearance of Help and Support service. I discovered
this while tracking a different error from within the event log. I received a
pop-up message indicating that I need to start the service named Help &
Support. I tried to open H&S from the start menu and it would not open. This
is not related to your FTP problem, but this is the first post I've seen
regarding SP2 issues. Anyone else have this problem?

"Dag Staale Jenssen" wrote:

> I haven’t realized this! I will call PSS.
> By the way, I have a SBS Standard R1 upgraded to R2 standard, upgraded to R2
> Premium where ISA Server 2004 will not install. It is interrupted because it
> can not install MSDE. I have googled log errors and tested 2 MVP workarounds.
> I am able to complete a sort of install. Thereafter I am running the SBS
> install “script” on the CD. ISA is then configured for SBS. When done, there
> seems to be some sort of a RPC issue. I therefore had to uninstall. Is this
> type of issue also PSS covered on PSS? I am currently about to use one of may
> TechNet support cases?
>
>
> "Dave Nickason [SBS-MVP]" wrote:
>
> > The WS03 SP does not require R2. But, there does appear to be some issue
> > with certain Premium users installing it. Hopefully more info will be
> > coming soon.
> >
> > This is a good opportunity for me to point out that it's a good idea for
> > people who have issues with service packs to call PSS (Microsoft Support).
> > Service pack support is free, and while you would not want to abuse that,
> > this type of issue is good to call on - more than one person seeing it, and
> > uninstalling the SP fixes it - they need to know that.
> >
> > "Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
> > message news:6DB219D9-877F-4FBE-9445-AB5554313EF3@microsoft.com...
> > > What I have come to realize, is that this SBS Server is a R1, CD for R2
> > > has
> > > arrived but it has not been installed. In requirement "R2" is used. This
> > > may
> > > or may not be related. But way did it then appear in Microsoft Update if
> > > it
> > > should not be applied? I chose to install after testing on a virtual
> > > server,
> > > there after may Action Pack installation. No problem so far whit those.
> > > The
> > > DHCP was delivering IPs, I did not have the time to test to investigate
> > > what
> > > was actually wrong. Employees where leaving work! I had to get the server
> > > up. On this particular server I am using Scope Option 161 and 162. I will
> > > take our advise, and thank you for your answer!
> >
> >
> >

I'm glad Microsoft has decided to directly support SP issues,
but it is still nice to have those issues discussed on this
forum. It is in forums like SBS that Microsoft gets real world
feedback for working systems. In fact, I remember that NT4
Server SP3 was probably the biggest failed service pack in MS
history. Users on the Server forum noted problems weeks before
MS acknowledge anything.

As a "community" we need to continue to use these newsgroups to
communicate with each other and Microsoft.

So call Microsoft, but post your experiences here, hopefully
some Microsoft hounds are snooping here as well.


In article <e#T2kf4ZHHA.4692@TK2MSFTNGP04.phx.gbl>,
gwdibble@NOSPAM.frontiernet.net says...
> The WS03 SP does not require R2. But, there does appear to be some issue
> with certain Premium users installing it. Hopefully more info will be
> coming soon.
>

Add this to SP2 issues: I have installed W2K3 SP2 on to SBS Server as
previous mentioned. SP2 remain on may one SBS Server for observation, on the
other it has been uninstalled. I can now add to SP2 issues that Server
Performance Report is no longer e-mail as usual on both installations.
Reports can be accessed in RWW but they are no longer e-mail to its
recipients.

On the box containing SP2, Monitoring and Reporting has been reset over the
night. I will now receive “No Performance data is available at this time.
Performance data is collected hourly.” The wizard has been run and time will
tell….

I have run the Performance and Monitoring Wizard on the box where SP2 was
uninstalled, and received the following event in the application log:

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Date: 17.03.2007
Time: 15:15:31
User: NT AUTHORITY\SYSTEM
Computer: SBS
Description:
A provider, PerfProv, has been registered in the WMI namespace,
ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the
HostingModel property. This provider will be run using the LocalSystem
account. This account is privileged and the provider may cause a security
violation if it does not correctly impersonate user requests. Ensure that
provider has been reviewed for security behavior and update the HostingModel
property of the provider registration to an account with the least privileges
possible for the required functionality.

Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Date: 17.03.2007
Time: 15:15:31
User: NT AUTHORITY\SYSTEM
Computer: SBS
Description:
A provider, PerfProv, has been registered in the WMI namespace,
ROOT\CIMV2\MicrosoftHealthMonitor\PerfMon, but did not specify the
HostingModel property. This provider will be run using the LocalSystem
account. This account is privileged and the provider may cause a security
violation if it does not correctly impersonate user requests. Ensure that
provider has been reviewed for security behavior and update the HostingModel
property of the provider registration to an account with the least privileges
possible for the required functionality.

Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 1016
Date: 17.03.2007
Time: 15:15:32
User: N/A
Computer: SBS
Description:
The data buffer created for the "EXOLEDB" service in the "C:\Program
Files\Exchsrvr\bin\exodbpc.dll" library is not aligned on an 8-byte boundary.
This may cause problems for applications that are trying to read the
performance data buffer. Contact the manufacturer of this library or service
to have this problem corrected or to get a newer version of this library.
Data:
0000: a4 eb 80 00 04 15 00 00 ¤ë€.....

Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 2003
Date: 17.03.2007
Time: 15:15:32
User: N/A
Computer: SBS
Description:
The configuration information of the performance library
"C:\WINDOWS\system32\infoctrs.dll" for the "InetInfo" service does not match
the trusted performance library information stored in the registry. The
functions in this library will not be treated as trusted.

Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 1016
Date: 17.03.2007
Time: 15:15:33
User: N/A
Computer: SBS
Description:
The data buffer created for the "MSExchangeIS" service in the "C:\Program
Files\Exchsrvr\bin\mdbperf.dll" library is not aligned on an 8-byte boundary.
This may cause problems for applications that are trying to read the
performance data buffer. Contact the manufacturer of this library or service
to have this problem corrected or to get a newer version of this library.
Data:
0000: 90 3e 87 00 ec 2b 00 00 >‡.ì+..
Event Type: Warning
Event Source: Perflib
Event Category: None
Event ID: 2003
Date: 17.03.2007
Time: 15:15:33
User: N/A
Computer: SBS
Description:
The configuration information of the performance library
"C:\WINDOWS\system32\ftpctrs2.dll" for the "MSFtpsvc" service does not match
the trusted performance library information stored in the registry. The
functions in this library will not be treated as trusted.

Check this out. If you try this fix, please post back with the result.
(Note that in addition to the described issues, the article references
"other symptoms that could be related.").

VPN, SecureNat/Nat and Outlook clients not working after installing Windows
Service Pack 2 in SBS 2003 Premium
http://blogs.technet.com/sbs/archive...3-premium.aspx

This is the official blog of the SBS support team, so you might want to
bookmark it for future reference.

"Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
message news:F6804D0F-D486-4DA4-9E54-AECF49656607@microsoft.com...
>I installed W2K3 SP2 on a SBS Premium. This particulate server is running
>an
> FTP site for thin clients. Information about the FTP site is passed to the
> thin clients by DHCP server. Thin Client could not access the FTP site
> after
> the installation. We could not find any reasonable explanation. This was
> preventing 120 users in a 40 device network from doing their job. We also
> noticed a slowdown of the network and had problems accessing the terminal
> server (slow logon) trough RDP on PCs. We therefore had to uninstall W2K3
> SP2. A server restart and the problem was resolved. Anny suggestions?

Are using newsreader on this blog and others. I am using a TechNet support
case on the ISA Server issue to have it resolved. When it comes to W2K3 SP2 I
will hang in there for a while. To se what the work brings out. There is also
another good link her:
http://msmvps.com/blogs/bradley/arch...ase-notes.aspx.
Tank you for answering and the link!

Please let us know the fix when your support incident is resolved. Thanks!


"Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
message news:97B7AEBB-4336-49E1-AE97-94DF5E235D7E@microsoft.com...
> Are using newsreader on this blog and others. I am using a TechNet support
> case on the ISA Server issue to have it resolved. When it comes to W2K3
> SP2 I
> will hang in there for a while. To se what the work brings out. There is
> also
> another good link her:
> http://msmvps.com/blogs/bradley/arch...ase-notes.aspx.
> Tank you for answering and the link!

"Dave Nickason [SBS MVP]" wrote:

> Please let us know the fix when your support incident is resolved. Thanks!
>
>
> "Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
> message news:97B7AEBB-4336-49E1-AE97-94DF5E235D7E@microsoft.com...
> > Are using newsreader on this blog and others. I am using a TechNet support
> > case on the ISA Server issue to have it resolved. When it comes to W2K3
> > SP2 I
> > will hang in there for a while. To se what the work brings out. There is
> > also
> > another good link her:
> > http://msmvps.com/blogs/bradley/arch...ase-notes.aspx.
> > Tank you for answering and the link!
>
>
>

"Dave Nickason [SBS-MVP]" wrote:

> The WS03 SP does not require R2. But, there does appear to be some issue
> with certain Premium users installing it. Hopefully more info will be
> coming soon.
>
> This is a good opportunity for me to point out that it's a good idea for
> people who have issues with service packs to call PSS (Microsoft Support).
> Service pack support is free, and while you would not want to abuse that,
> this type of issue is good to call on - more than one person seeing it, and
> uninstalling the SP fixes it - they need to know that.
>
> "Dag Staale Jenssen" <DagStaaleJenssen@discussions.microsoft.com> wrote in
> message news:6DB219D9-877F-4FBE-9445-AB5554313EF3@microsoft.com...
> > What I have come to realize, is that this SBS Server is a R1, CD for R2
> > has
> > arrived but it has not been installed. In requirement "R2" is used. This
> > may
> > or may not be related. But way did it then appear in Microsoft Update if
> > it
> > should not be applied? I chose to install after testing on a virtual
> > server,
> > there after may Action Pack installation. No problem so far whit those.
> > The
> > DHCP was delivering IPs, I did not have the time to test to investigate
> > what
> > was actually wrong. Employees where leaving work! I had to get the server
> > up. On this particular server I am using Scope Option 161 and 162. I will
> > take our advise, and thank you for your answer!
>
>
> I installed the SP2 onto a SBS server Standard Edition, boot up took 2 hours and then the server would not shutdown. I launched the uninstall which just sat at the inspecting system until I could not wait anymore, approximately 12 hours. Now I was really stuck as I can not uninstall SP2, so I took your advice and called Microsoft Tech support and told them that I had a Service Pack issue. The response was that it did not mater what the issue was I needed to cough up $295.00 before I could talk to anyone. Not feeling that I should be funding their troubleshooting of this issue I decided to do a restore to my last good backup and fix the problem that way. I am now up and running again and looking forward to the day that Microsoft does not push down updates that screw up your server.