SoftwareTipsandTricks Forum

Go Back   SoftwareTipsandTricks Forum > Operating Systems > Windows XP
User Name
Password


Logon script problem

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes

  #1  
Old 01-30-2003, 07:18 PM
static1701 Offline
Junior Member
 
Join Date: Jan 2003
Posts: 5
Unhappy Logon script problem

Hello,

I have a Windows 2000 server, and window XP workstations on my home network. The problem that I have is my logon script fails to run for some of my users (family members) and then it runs at other times.

I have logon.cmd in the netlogon share on the server, it just maps shares. I can click on it from any machine and it will run and map the shares just fine.

I could understand it if it did not work at all, but when it works some of the time for some of the users... It does not make sense.

Any one have any ideas?

Static
Reply With Quote

  #2  
Old 01-30-2003, 07:22 PM
dave_in_aus Offline
Junior Member
 
Join Date: Dec 2002
Posts: 4
do the logon scripts appear in the account properties of each user?
Reply With Quote

  #3  
Old 01-30-2003, 09:01 PM
Pakalolo's Avatar
Pakalolo Offline
Junior Member
 
Join Date: Jan 2003
Posts: 21
Are using Group Policy to assign the User's Logon script?

If you are, did you know: under Win2000 When a logon script is run- Group Policy-based logon scripts are run hidden and asynchronously by default. Unlike Windows NT 4.0 scripts.

To assign user logon scripts via/Group Policy

Quote:
1. Open the Group Policy snap-in.

2. In the console tree, click the Scripts node.

3. In the details pane, double-click the Logon icon.

4. In the Logon properties page, click Add.

5. In the Add a Script dialog box, set the options you want to use, and then click OK:

6. Script Name: Type the path to the script, or click Browse to search for the script file in the Netlogon share of the domain controller.

7. Script Parameters: Type any parameters you want to use as you would type them on the command line. For example, if your script included parameters called //logo (display banner) and //I (interactive mode), you would type the following:
//logo //I

8. In the Logon properties page, specify any options you want to use:

9. Logon Scripts for: Lists all scripts currently assigned to the selected Group Policy object. If you assign multiple scripts, the scripts are processed according to the order you specify. To move a script up in the list, click it and then click Up; to move it down, click Down.

10. Add: Opens the Add a Script dialog box, where you can specify any additional scripts to use.

11. Edit: Opens the Edit Script dialog box, where you can modify script information such as name and parameters.

12. Remove: Removes the selected script from the Logon Scripts list.

13. Show Files: Select to view the script files stored in the selected Group Policy object.

NOTE: Logon scripts are run as User, not Administrator.

Hope that sheds some light...

Pakalolo
Reply With Quote

  #4  
Old 02-01-2003, 02:47 PM
static1701 Offline
Junior Member
 
Join Date: Jan 2003
Posts: 5
Logon script

Hello,

I am not using the group policy to do the logon script. I just have it defined in the users profile. The same way that I did under NT4.

Are you saying that I have to make the setting on the users machine under group policy?

When I bring up the group policy on the serve it says it is for the local machine.

Thanks for the help,

Static
Reply With Quote

  #5  
Old 02-01-2003, 06:50 PM
Pakalolo's Avatar
Pakalolo Offline
Junior Member
 
Join Date: Jan 2003
Posts: 21
Smile Hey static-

It sounds like you have a good grasp of the NT4 domain architecture, Me too! We have obviously been around for awhile... LOL

Quote:
I am not using the group policy to do the logon script. I just have it defined in the users profile. The same way that I did under NT4.

that's what I figured and the reason why I replied with the previous information...

Under Win2000- Active Directory or AD needs to be implemented before your server can act as the primary domain controller for your LAN. Unfortunately the AD structure used by Win2000 is nowhere near what we were used to with NT4. I like the old way of doing things a lot better! To me AD is a piece of CR*P (sorry, ) but it's more like Novell then, well... novell!

Quote:
Are you saying that I have to make the setting on the users machine under group policy?
Since your Win2000 server is not acting as the PDC of your LAN- I am not clear on what steps to take in order to troubleshoot this. I do know that if one of my clients was unable to run a login script from my PDC- the "AD Group Policy" MMC would definitely be where I would go to resolve it...

Sorry, but I haven't played around a lot with login scripts on a standalone server. If I were to guess- I would definitely go to the client machine and see what group policy had to offer on the local level.

Normally- I wouldn't implement a login script unless the client was logging on to a PDC or BDC and needed it to access or share domain resources...

Quote:
When I bring up the group policy on the serve it says it is for the local machine.
This is why I have never used a login script on a standalone server.

I know this doesn't help you out that much and I apologize... When I first read your post I assumed your machine was the PDC of your LAN and the fix would be a slam dunk (group policy/not like NT4, yes! )...

Not!

Oh well, sorry again-

Good Luck!

Pakalolo

ps- if you do end up promoting your machine as the PDC let me know if there is anything I can help out with
Reply With Quote

  #6  
Old 02-01-2003, 08:21 PM
static1701 Offline
Junior Member
 
Join Date: Jan 2003
Posts: 5
PDC

Hello,

I have to agree, I like NT4 much better but because work was upgrading... I upgraded at home to keep my skills up.

My server is the PDC on my network, it is setup to do DNS,DHCP and print services. I do have active dirrectory running, all of my family members have an account. All of my work stations are XP.

As I type to you, my login script worked fine and I have an H: mapped to my server, by buddy that is over is on another machine and his H: did not map.

Everytime I try load the group snapin, it tells me that I am dealing with the local group. I take it I need to be editing the domain group?

I just find the whole thing to be a pain since I spent all day friday on tech net looking for an answer as well as reading the book I have.

Thanks for the quick responses,

Static
Reply With Quote

  #7  
Old 02-01-2003, 09:21 PM
Pakalolo's Avatar
Pakalolo Offline
Junior Member
 
Join Date: Jan 2003
Posts: 21
Thumbs up Hey Static-

I agree with you about NT4, Win2k is a good learning experience if you've got the time!

I gotta run right now and pick up my nephew from the airport-

I was just curious, are you trying to work with the Group policy snapin from your workstation or the server? Load the Win2k resource kit onto your workstation and that should make life easier...

One more thing- You said that your account ran the login script when you last logged in, are you or the account that you are using to login to the workstation part of the domain administrators group?

Gotta run right now-

I'll check back when I get home to see how you're doing!

Good luck!

Pakalolo
Reply With Quote

  #8  
Old 02-01-2003, 09:59 PM
static1701 Offline
Junior Member
 
Join Date: Jan 2003
Posts: 5
Logon script

Hello,

I am working on it from the server, The server is logged on as the administrator. I am logged on to a workstation with my account and I do have admin rights.

Is the resource kit on the install disc?
I will take a look for it.

Thanks,

Static
Reply With Quote

  #9  
Old 02-02-2003, 01:04 AM
Pakalolo's Avatar
Pakalolo Offline
Junior Member
 
Join Date: Jan 2003
Posts: 21
Smile Static-

Hi,

This is the tool that I think you are looking for-Windows 2000 Resource Kit Tool: FAZAM2000
Overview
FAZAM 2000 provides administrators with group policy management from a central, easy-to-use console.

Unfortunately the resource kit isn't on the Win2000CD. I don't know why it wasn't. I think that it would have been a good thing to include. You can get it for free with a Technet or MSDN subscription. Otherwise, you have to buy the Resource kit book or download the tools individually. Here are some links to the individual downloads and other useful documentation from the resource kit, check 'em out I think you'll find them useful-

Windows 2000 Server Resource Kit Tools

Windows 2000 Resource Kit (Free Tool Downloads) a more comprehensive list)

Resource Kits

Pakalolo
Reply With Quote

  #10  
Old 02-02-2003, 04:37 PM
static1701 Offline
Junior Member
 
Join Date: Jan 2003
Posts: 5
Add on tools / Group Policy

Hello,

Thanks for the links, I tried the first one and I see what it is doing. It seems to let me edit the policy for a user on a given computer. I suppose that I could do it that way, but why did MS leave the logon script option in the user profile screen if it is not going to work? Seems like they went out of their way to make it harder to use.

The wife is calling so I can't mess with it any more this evening. I will download the other tomorrow. Thanks for all your help.

Static
Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
XP Networking Problem: 'Logon Failure' focussed Windows XP 15 09-27-2006 08:12 AM
Windows xp logon problem aljabr Windows XP 2 11-25-2004 12:03 PM
Possible XP - Java script problem Blackford Windows XP 4 03-29-2004 09:53 PM
windows xp logon problem chris the drago Windows XP 2 12-31-2003 12:57 PM
UNbelievable problem on session logon XP fishbone Windows XP 3 12-26-2003 08:30 PM



All times are GMT -5. The time now is 03:55 AM.


Designed by eXtremepixels. Powered by vBulletin Version 3.5.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 2.3.2 © 2005, Crawlability, Inc.