RE: Backup issues after changing administrator name



Hello,

Thank you for posting back.

Please see my suggestions below:

1. Make sure that the steps you changed the administrator name was correct.

You can either manually rename the Administrator account on the computer
running SBS 2003, or, using GPMC, you can automatically rename all the
Administrator account names in the network (including the server). So, if
you just want to rename the Administrator account on the server itself, you
can just use the manual listed below:

To complete this procedure, you must be logged on as a member of the Domain
Admins security group.

1): Open Server Management.

2): In the console tree, click Users.

3): In the details pane, right-click Administrator, and then click
Properties.

4): On the General tab, in the Display text box, replace the previous name
(Administrator) with a new name.

5): On the Account tab, in the User logon name box, type the new name.

6): In the User logon name (pre-Windows 2000) box, replace the previous
user logon name (Administrator) with the new name, and then click OK.

7): After changing the Administrator account name, you need to log off and
then use the new name to log back on as an administrator on the server.

Make sure:

1): Rename the Administrator account only after completing all the tasks
in the To Do List.

2): After changing the Administrator account name, you need to log off and
then use the new name to log back on as an administrator on the server.

2. Go to Server Management\Standard Management\To Do List, re-run the
Backup Wizard.

3. Make sure the Volume Shadow Copy Service is Started. On the SBS 2K3
server, run "services.msc" you will find are in Volume Shadow Copy, make
sure it is started, if not, right click it and select Start.

4. I need you to re-run the backup and paste me the full content of the
event log (Include the error ID).

I am appreciated your time. I am looking forward to hearing from you soon.

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • Re: Web Server - User Access and Priviledges.
    ... It makes sense to have more than the built in administrator account. ... For the IIS 5.0 server be sure to consider ... running the IIS Lockdown/URLscan tool if you have not already but I would recommend ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Web Server - User Access and Priviledges.
    ... It makes sense to have more than the built in administrator account. ... For the IIS 5.0 server be sure to consider ... running the IIS Lockdown/URLscan tool if you have not already but I would recommend ...
    (microsoft.public.windows.server.security)
  • Re: Web Server - User Access and Priviledges.
    ... It makes sense to have more than the built in administrator account. ... For the IIS 5.0 server be sure to consider ... running the IIS Lockdown/URLscan tool if you have not already but I would recommend ...
    (microsoft.public.security)
  • Re: Web Server - User Access and Priviledges.
    ... It makes sense to have more than the built in administrator account. ... For the IIS 5.0 server be sure to consider ... running the IIS Lockdown/URLscan tool if you have not already but I would recommend ...
    (microsoft.public.inetserver.iis.security)
  • Re: Web Server - User Access and Priviledges.
    ... It makes sense to have more than the built in administrator account. ... For the IIS 5.0 server be sure to consider ... running the IIS Lockdown/URLscan tool if you have not already but I would recommend ...
    (microsoft.public.win2000.security)

Loading