WinXP Pro SP2
1GB RAM
Office 2003
Win2K3 SP1 SBS Network

Issue #1: While logged on as an Administrator (or even a user with
Administrator privileges) on this workstation (with WinXP Pro SP2) connected
to the Win2K3 SP1 SBS network, I'm getting a message "An access denied error
was returned while attempting to change a service. You may need to log on
using an Administrator account to make the specified changes."

The scenario is changing 'msconfig' to not allow certain services to start
or not start at startup. When I click on Apply or OK, it appears that the
desired changes I want are saved but I get the above message anyway. I get
this message regardless of being logged onto the network or not. Hence, is
may be specific to this workstation's issue.

Issue #2 (may be related to Issue #1): Also, I am setting up this PC at the
office on a Win2K3 SBS network. I have setup the user with a previous
workstation which crashed. Now, when I use the new workstation (this one), I
can get to the network and do what I need to do but it appears that Win2K3
and Exchange Server 2K3 aren't FULLY recognizing the workstation. So, things
are fine on the network relative to this workstation either as Administrator
or "UserID01" except for the Exchange Server2K3 issue which impacts the
Outlook 2003 setup-which can't be completed! I'm pretty sure the Exchange
Server 2K3 issue is a 'network authentication' issue, but I'm not sure where
to go. I am using specific IP addresses such as 192.168.1.103 with no
conflicts on the network. Both my wired and my wireless network work fine
except for the above issues (to my knowledge)
Suggestions appreciated on BOTH issues which MAY be interrelated.
TIA,
Tom

This is what <Tom> shared with us today ...

>WinXP Pro SP2
>1GB RAM
>Office 2003
>Win2K3 SP1 SBS Network
>
>Issue #1: While logged on as an Administrator (or even a user with
>Administrator privileges) on this workstation (with WinXP Pro SP2) connected
>to the Win2K3 SP1 SBS network, I'm getting a message "An access denied error
>was returned while attempting to change a service. You may need to log on
>using an Administrator account to make the specified changes."
>
>The scenario is changing 'msconfig' to not allow certain services to start
>or not start at startup. When I click on Apply or OK, it appears that the
>desired changes I want are saved but I get the above message anyway. I get
>this message regardless of being logged onto the network or not. Hence, is
>may be specific to this workstation's issue.
>
>Issue #2 (may be related to Issue #1): Also, I am setting up this PC at the
>office on a Win2K3 SBS network. I have setup the user with a previous
>workstation which crashed. Now, when I use the new workstation (this one), I
>can get to the network and do what I need to do but it appears that Win2K3
>and Exchange Server 2K3 aren't FULLY recognizing the workstation. So, things
>are fine on the network relative to this workstation either as Administrator
>or "UserID01" except for the Exchange Server2K3 issue which impacts the
>Outlook 2003 setup-which can't be completed! I'm pretty sure the Exchange
>Server 2K3 issue is a 'network authentication' issue, but I'm not sure where
>to go. I am using specific IP addresses such as 192.168.1.103 with no
>conflicts on the network. Both my wired and my wireless network work fine
>except for the above issues (to my knowledge)
>Suggestions appreciated on BOTH issues which MAY be interrelated.
>TIA,
>Tom

Hello Tom,

Does the machine that you are trying to setup have the same "Computer
Name" as the one that crashed?
If so...try naming it to an unused and uniqe computer name.
A client machine can cache login information once its been joined to a
domain even though its being logged onto locally.

Respectfully,

Trev

(Hoping to be voted MS-MVP)

Good question, Trevor. Both are Dell laptop/workstations. No both machines
have a different name entirely.
Other ideas or approaches?

"Trevor" wrote:

> This is what <Tom> shared with us today ...
>
> >WinXP Pro SP2
> >1GB RAM
> >Office 2003
> >Win2K3 SP1 SBS Network
> >
> >Issue #1: While logged on as an Administrator (or even a user with
> >Administrator privileges) on this workstation (with WinXP Pro SP2) connected
> >to the Win2K3 SP1 SBS network, I'm getting a message "An access denied error
> >was returned while attempting to change a service. You may need to log on
> >using an Administrator account to make the specified changes."
> >
> >The scenario is changing 'msconfig' to not allow certain services to start
> >or not start at startup. When I click on Apply or OK, it appears that the
> >desired changes I want are saved but I get the above message anyway. I get
> >this message regardless of being logged onto the network or not. Hence, is
> >may be specific to this workstation's issue.
> >
> >Issue #2 (may be related to Issue #1): Also, I am setting up this PC at the
> >office on a Win2K3 SBS network. I have setup the user with a previous
> >workstation which crashed. Now, when I use the new workstation (this one), I
> >can get to the network and do what I need to do but it appears that Win2K3
> >and Exchange Server 2K3 aren't FULLY recognizing the workstation. So, things
> >are fine on the network relative to this workstation either as Administrator
> >or "UserID01" except for the Exchange Server2K3 issue which impacts the
> >Outlook 2003 setup-which can't be completed! I'm pretty sure the Exchange
> >Server 2K3 issue is a 'network authentication' issue, but I'm not sure where
> >to go. I am using specific IP addresses such as 192.168.1.103 with no
> >conflicts on the network. Both my wired and my wireless network work fine
> >except for the above issues (to my knowledge)
> >Suggestions appreciated on BOTH issues which MAY be interrelated.
> >TIA,
> >Tom
>
> Hello Tom,
>
> Does the machine that you are trying to setup have the same "Computer
> Name" as the one that crashed?
> If so...try naming it to an unused and uniqe computer name.
> A client machine can cache login information once its been joined to a
> domain even though its being logged onto locally.
>
> Respectfully,
>
> Trev
>
> (Hoping to be voted MS-MVP)
>