R
Randy Wilson
We have upgraded our entire domain to Windows2003 (except one DC that is
sitting in a closet --locked up and out of the way). So far, we have not
had any problems except the one below. The terminal services machine below
was a fresh install of 2003.
We use terminal services to allow some of our field staff to connect to the
network when out of the office. When they dialed into the TS server, they
got in fine under W2K. In 2003, it tells them that they do not have
permission to log on locally. I have changed the Local Security policy to
allow this group to log on locally, and get the same error.
The only thing that I found on MS support was about ownership of roaming
profiles and that is not the issue either. As I told my boss, in the world
of fixes, "there are fixes that work and there are fixes that work for NOW".
The latter allowed me to go home for the weekend but the fix for NOW was to
make the group local administrators on the box, which I don't care about
because they cannot do anthing with that box anyway due to other controls
put into effect, but of course with Windows 2003, only one administrator can
be logged in at a time -- as soon as the next logs in, it logs the prior
user out.
Licensing is not an issue for us, so don't slam me for that -- we have
plenty of licenses for this machine's legal use. I think I will end up
restoring the machine to its 2000 state and trying an inplace upgrade to
2003.
sitting in a closet --locked up and out of the way). So far, we have not
had any problems except the one below. The terminal services machine below
was a fresh install of 2003.
We use terminal services to allow some of our field staff to connect to the
network when out of the office. When they dialed into the TS server, they
got in fine under W2K. In 2003, it tells them that they do not have
permission to log on locally. I have changed the Local Security policy to
allow this group to log on locally, and get the same error.
The only thing that I found on MS support was about ownership of roaming
profiles and that is not the issue either. As I told my boss, in the world
of fixes, "there are fixes that work and there are fixes that work for NOW".
The latter allowed me to go home for the weekend but the fix for NOW was to
make the group local administrators on the box, which I don't care about
because they cannot do anthing with that box anyway due to other controls
put into effect, but of course with Windows 2003, only one administrator can
be logged in at a time -- as soon as the next logs in, it logs the prior
user out.
Licensing is not an issue for us, so don't slam me for that -- we have
plenty of licenses for this machine's legal use. I think I will end up
restoring the machine to its 2000 state and trying an inplace upgrade to
2003.