Recommended Posts

I am trying to create a login script that will map user drives based on the groups they belong to. I am using ifmember.exe from the Windows 2000 Resource Kit. However, it appears to be working on my XP box, but it's causing my 2000 box to lock up. This leads me to believe there is an error in the script. The Groups I have are CGS, DATABOOK, PROGRAMS and ADMINISTRATORS.

The script:

net use /persistent:no

ifmember CGS

if not errorlevel 1 goto SkipU

NET USE /User:dc1\%username% U: \\dc1\HOME$\%USERNAME%

if errorlevel 1 set LS_Error=%LS_Error% U (Home)

:SkipU

ifmember CGS

if not errorlevel 1 goto SkipM

NET USE /User:dc1\%username% M: \\dc1\GROUP$\public

if errorlevel 1 set LS_Error=%LS_Error% U (Home)

:SkipM

ifmember Databook

if not errorlevel 1 goto SkipN

NET USE /User:dc1\%username% N: \\dc1\GROUP$\databook

if errorlevel 1 set LS_Error=%LS_Error% N (DATABOOK)

:SkipN

ifmember Programs

if not errorlevel 1 goto SkipO

NET USE /User:dc1\%username% O: \\dc1\Programs$

if errorlevel 1 set LS_Error=%LS_Error% O (PROGRAMS)

:SkipO

ifmember Administrators

if not errorlevel 1 goto SkipQ

NET USE /User:dc1\%username% Q: \\dc1\Software$\Apps

if errorlevel 1 set LS_Error=%LS_Error% Q (APPS)

I am not sure what the persistance tag means at the begining or the ir error the "if errorlevel 1 set LS_Error=%LS_Error%" line in the script means. So, if someone could explain those, I would appreciate it.

Link to comment
https://www.neowin.net/forum/topic/83939-login-script-problems/
Share on other sites

persistent tag simply allows you to re-establish the network connected shares for a user when they log in into your network.....this is set to either yes or no....and I think you know that part already....the errorlevel line allows a way for you to gracefully exist the script if your users don't meet the conditions set forth by which groups the user belongs to...if they do meet the conditon...it goes about allowing the user to gain access to set shares...

hmmmm...not sure...but you say that it locks up your W2K system....so you mean to say that you actually SEE the script execute when logging in....but it FREEZES at that point...so you see the login script dialog box forzen on your screen?....and that leave no alternative but to reboot?

...it happened to me when I migrated an NT 4.0 box to W2K and it caused the scripts to be unavailable...

You're not setting the variable for the LS_Error parameter

On your NET USE line you have "/User:dc1\%username%", you shouldn't need to specify the user since it will use the current account unless specified otherwise (I could see using it if you wanted to map with a different account name)

In the "ifmember Administrators" section you have "if not errorlevel 1 goto SkipQ" but don't have a "SkipQ" defined (guessing you just missed pasting it?)

This link should get you running:

http://www.experts-exchange.com/Operating_...Q_20420238.html

Thanks guys, I got it working. It turns out it was freezing because the profile had someone got corrupt. I deleted the profile and it worked fine. I did change the script a little, don't use the one I pasted for reference. PM me if you need help and I will do my best.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Ah .. lockout for suspicious activity. I bet they uploaded the SanDisk utility detected as malware
    • Microsoft 365 will soon disable outdated authentication protocols for file access by Usama Jawad On a fairly regular basis, Microsoft disables outdated protocols that are used to access its services. In the past few years, the company has deprecated Basic Auth in Exchange Online and cut access to Outlook for third-party apps relying on this protocol. Now, it has decided to get rid of old authentication protocols for file access across Microsoft 365 services. As reported by Bleeping Computer, Microsoft has posted a message on its Microsoft 365 Admin Center. Starting from mid-July 2025, the company will begin disabling legacy authentication protocols used to access files across Microsoft 365 and Office apps, SharePoint, and OneDrive. Essentially, applications or services which use the Relying Party Suite (RPS) or FrontPage Remote Procedure Call (FPRPC) will to perform browser-based authentication to perform open operations on Office files will no longer be able to do so. As expected, this is primarily being done to improve the cybersecurity posture of various services. Microsoft states that RPS can be brute-forced and phished with relative ease as it is fairly outdated. Similarly, FPRPC is typically used for remote web page authoring and it is susceptible to exploitation through various vulnerabilities too. As such, both of these protocols will be disabled by default starting from mid-July 2025, with the rollout of this change targeting completion by August 2025. The Redmond tech giant will update the protocol baseline by default without mandating any licensing changes for customers. In addition, once these modifications are rolled out, Microsoft 365 will require admin consent to get third-party access to files and sites. IT admins can view the guidance available here to configure admin consent workflows. Microsoft says that these changes align with the principles of its Secure Future Initiative (SFI). Earlier today, it announced the rollout of improved security defaults for Windows 365 citing the same reasons too.
    • It does and it can... I took an i3 board and upgraded it to my FX8350... no issues, just put in new drivers over the top that Windows didn't. Not the issue for me, (though I eventually did do a new install from 23H2 to 24H2)... I was on 22H2 at the time. The issue is activation. You may get hit with having to activate again.
  • Recent Achievements

    • First Post
      Fuzz_c earned a badge
      First Post
    • First Post
      TIGOSS earned a badge
      First Post
    • Week One Done
      slackerzz earned a badge
      Week One Done
    • Week One Done
      vivetool earned a badge
      Week One Done
    • Reacting Well
      pnajbar earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      707
    2. 2
      ATLien_0
      283
    3. 3
      Michael Scrip
      218
    4. 4
      +FloatingFatMan
      197
    5. 5
      Steven P.
      130
  • Tell a friend

    Love Neowin? Tell a friend!