S
Sandra L Miller
I just installed Windows Server 2003 on a machine that had been
running Windows 2000 Server (clean install, not upgrade). During
the installation process, I must have inadvertently clicked some
security setting, because I cannot install some software (in this
case, Mozilla Firefox, Secure Shell). I have 4 other Windows Server
2003 machines (plus hundreds of Windows XP desktop machines) on
which these items have been installed with no problems.
The error message I get is, "Windows cannot access the specified
device, path, or file. You may not have the appropriate permissions
to access the item."
I have tried both a local admin account and a domain admin account.
I can copy the executables to the desktop (from another server),
but cannot run the .exe files.
I *was* able to install Microsoft SQL Server.
Does anybody have any ideas?
Thanks,
Sandy
--
Sandra L Miller
Windows System Administrator
Department of Computer Science
University of Arizona
"The opinions or statements expressed herein are my own and should not be
taken as a position, opinion, or endorsement of the University of Arizona."
running Windows 2000 Server (clean install, not upgrade). During
the installation process, I must have inadvertently clicked some
security setting, because I cannot install some software (in this
case, Mozilla Firefox, Secure Shell). I have 4 other Windows Server
2003 machines (plus hundreds of Windows XP desktop machines) on
which these items have been installed with no problems.
The error message I get is, "Windows cannot access the specified
device, path, or file. You may not have the appropriate permissions
to access the item."
I have tried both a local admin account and a domain admin account.
I can copy the executables to the desktop (from another server),
but cannot run the .exe files.
I *was* able to install Microsoft SQL Server.
Does anybody have any ideas?
Thanks,
Sandy
--
Sandra L Miller
Windows System Administrator
Department of Computer Science
University of Arizona
"The opinions or statements expressed herein are my own and should not be
taken as a position, opinion, or endorsement of the University of Arizona."