Bad upgrade

[Bronson Dant]

We had someone do an upgrade of a server from w2k to w2k3. They
started the upgrade process from a WTS session. After all was said and
done, the upgrade is now having some big issues. All files on the C:
drive are now set to read-only and we cannot remove this attribute.
There was some issues at logon also. Can anyone point me in the
direction to explain why it is not a good idea to do this again. I
need specific technical reasons. I know it does not work but need to
explain why.

 

[Guest]

Can you be a little more specific as to the errors you're experiencing, system/application event log errors, services not starting?

Are individual files marked read-only, or are you looking at the properties of a folder?

Does the server boot, as if all files are read only there's no way the machine would even boot.

Was this done while the installer was in the local office, or from a remote location?

A alternative way to install the OS would be to deliver a sysprep image via CD/DVD along with an answer file to automate the installation, or to use RIS. These however do clean installs, not upgrades.

I searched on google & groups.google.com and couldn't find any matched to upgrading via remote desktop, but then again I never considered it an option.

I'm interested in hearing more about this situation.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

----- Bronson Dant wrote: -----

We had someone do an upgrade of a server from w2k to w2k3. They
started the upgrade process from a WTS session. After all was said and
done, the upgrade is now having some big issues. All files on the C:
drive are now set to read-only and we cannot remove this attribute.
There was some issues at logon also. Can anyone point me in the
direction to explain why it is not a good idea to do this again. I
need specific technical reasons. I know it does not work but need to
explain why.