FYI, MS has changed the secedit command in 2003. To force a policy refresh,
the command is gpupdate.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
roddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/stan
dard/proddocs/en-us/RefrGP.asp
Regards,
Timothy Harkin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, April 19, 2004 12:40 PM
To: [EMAIL PROTECTED]
Subject: RE: Users can't login to UV after upgrade from NT4 to 2003 SBS
Here are the notes that I have been using (for UD):
Open AD Users and Computers.
Create a Global group
Add members to group accordingly, then assign directory rights accordingly.
Click Start - Programs - Administrative Tools and click Domain Controller
Security Policy.
Double click the Security Settings folder, double click Local Policies, and
then click User Rights Assignment.
Under the Policy column, click Logon Locally, and then click Add.
Click Browse, select the appropriate group, then click Add.
Click Ok, click Ok, click Ok.
Open a command prompt and type the following command:
secedit /refreshpolicy machine_policy /enforce
Press Enter twice.
I also have a PDF document from IBM which indicates to update the local
security policy and then the domain security policy and add log on locally
and access this computer from the network rights.
I think the secedit /refreshpolicy may be the key as I believe it can
sometimes take some time for your changes to take effect.
hth
--
Colin Alfke
Calgary, Alberta Canada
Just because something isn't broken doesn't mean that you can't fix it
Stu Pickles
-Original Message-
From: Joe Walter [mailto:[EMAIL PROTECTED]
Sent: Monday, April 19, 2004 10:31 AM
To: [EMAIL PROTECTED]
Subject: Users can't login to UV after upgrade from NT4 to 2003 SBS
Having a strange problem at a client site.
There sysadmins upgraded the server running Universe from NT4
to Windows
2003 Small Business Server.
Everything seemed OK, until regular domain users tried to
login to universe.
It seems to accept username/password but then telnet session terminates
immediately afterward.
Only two users can log in. Both of these users where members of the
administrators group.
All other users where members of Domain Users and a special
group called
UVUsers which we setup and granted the right to 'logon
locally'. We checked
to ensure the group UVUsers had right to logon locally - it
did. We then
removed and recreated the group UVUsers and gave it rights to
logon locally
- that still didn't work.
Now here is the really bizarre thing. EVEN if we add any of the regular
users to the administrators group - THEY STILL CAN'T LOGIN TO UNIVERSE.
Only those two users that happened to be members of the
administrators group
when the server was upgraded are able to login.
I'm stumped.
Any ideas greatly appreciated.
Thanks,
joe
Joe Walter
Fax/Voice mail: 1.435.514.5132
http://jaw1.home.mindspring.com
Did you ever stop to think, and forget to start again?
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
