Jump to content

DrUltima

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by DrUltima

  1. nmX.Memnoch, I tried your printer migration script and it works very well. Thank you. I was wondering how I could bypass the 00 that shows up after each migration? I want to see an error message if any exists, but if any does not, I want to not see the 0. Thanks for your thoughts.
  2. For Users' individual shares, I use the profile in AD. If that fails, I have this as a scripted backup: IF @HOMESHR="" COLOR r+/n ? " Notice! No Homeshare Drive defined for @USERID" ELSE ? " Connecting Drive @HOMEDRIVE to @HOMESHR" USE @HOMEDRIVE /del USE @HOMEDRIVE "@HOMESHR" IF @ERROR < 0 COLOR r+/y+ ? ''+@ERROR+' - '+@SERROR SLEEP 15 COLOR w/n ENDIF ENDIF I would love to see this. I did this once before in an old company, but all I had to do was populate a file called printers.ini. I ended up doing this for the server check, thanks to some help from the KixTart forum: IF NOT INSTR(@ProductType,'Workstation') AND NOT INSTR(@ProductType,'Professional') ? "Bypassing the login script because you are logging in from a " + @ProductType + "!" GOTO end;bypassing the rest of this script - I know I could use EXIT, but I like this more. ELSE ? "Because you are connecting from a @ProductType workstation I am continuing your login script." ENDIF I had never thought of forcing allowable pop up sites in XPSP2. Good call. On the screen saver timeout... Is that in seconds? (probably should be obvious, but I would rather check than assume) Thanks again!
  3. Thanks for the offer! I would love to take you up on it. jyrwin was correct in that this GPO will take care of questions 1 and 2 and 3, so thanks! While I was hoping to be able to script this, since I have since found out all clients are on Windows 2000 or better, I will just set the two GPO settings needed to pull this off. I do want to do things like migrate printers from one server to another, establish printer lists based on both userid and computer name, may drives based on group membership, etc, so I would be very intersted to see your script! Thanks for the offer. Here is mine thus far, keeping in mind that only I and one non-IS volunteer guinea pig are running it. ; ************************************************************************ ; * My company name KiXtart logon script for ALL Domains. * ; ************************************************************************ ; * Author: Justin Owens * ; * Created: April 6, 2006 * ; *----------------------------------------------------------------------* ; * Modified By: * ; * Date Modified: * ; * Reason for Mod: * ; ************************************************************************ $UID = @UserID $PT = @ProductType ; ************************************************************************ ; * Here we are just giving the login user a welcome message. * ; ************************************************************************ COLOR w+/n ? "Welcome to the Company Name Here Network" COLOR y+/n ? "You are logging in as @userid." ? "You are logging in from a @ProductType computer." ? "" COLOR w/n ; ************************************************************************ ; * Here we are shortcuting the server type operating systems so that * ; * we can use them later to make sure scripts don't run on a server. * ; ************************************************************************ $Win2000 = "Windows 2000 Server" $Win2000DC = "Windows 2000 Domain Controller" $Win2003 = "Windows Server 2003" $Win2003DC = "Windows Server 2003 Domain Controller" $Win2003R2 = "Windows Server 2003 R2" $Win2003R2DC = "Windows Server 2003 R2 Domain Controller" ;Actual Stuff goes here if $UID = "myuserid"; will change this to group membership catch when ready to test with rest of IS ? "Hello, " + @fullname;Should be my name ; You never want to run a script when logged into a server. It can cause all kinds of problems. So... if $PT = $Win2000 OR $Win2000DC OR $Win2003 OR $Win2003DC OR $Win2003R2 OR $Win2003R2DC;want a shorter way to do this ? "Bypassing the login script because you are logging in" ? "from a " + $PT + "!" GoTo end;bypassing the rest of this script else ? "I can see that you are logging in from a " + $PT + " computer." endif else ? "I can see that you are logging in from a " + $PT + " computer, but" ? "you are not Justin! Bypassing login script." ? "How did you manage to run this script?" GoTo end;so if I add more stuff after the endif it wont run for this user endif :end sleep 15;I want to see what has run exit Thanks for the assist!
  4. Hello... First time poster, so please be patient. I am trying to set up a login script on a Windows 2003 AD. I have used the Kix scripts in the past in other companies and very much like them. It is currently set up as follows: 1) Currently, I just have one person running a login script (me). 2) I am calling it by adding this to my User Profile in AD: %0\..\login.bat 3) The contents of login.bat is: %0\..\kix32 %0\..\login.kix 4) The contents of login.kix is: ? "Hello." sleep 5 exit 5) The script runs, but runs minimized and Windows XP Pro continues to login to the desktop. Here are my best practice questions: 1) How can I get it to NOT be minimized? 2) How can I prevent the rest of Windows from loading until the KiXtart script is finished? 3) How can I accomplish one of those boxes that makes you sell your soul to the company or be logged out? Thanks for the assistance!
×
×
  • Create New...