Sign in to follow this  
Followers 0
Iznogoud

[Login Script] Do's and don'ts

7 posts in this topic

#1 ·  Posted (edited)

I install and deliver many server environments and for the loginscript part i am using KIX32.

This works perfectly, but the old DOS screen is bugging me since i learned a bit of AutoIT. So i tried KixForms, but this is way to hard to understand and no easy logic.

I want to do this with AutoIT and the following commands keeps returning so if i can find the best way to do this in AutoIT i can create a nice window with logo etc. and text that updates while the login process is running on.

Kix32 Commands:

  • @PRODUCTTYPE
  • USE
  • AddPrinterConnection
  • InGroup
  • SetDefaultPrinter
  • Shell %COMSPEC%....
  • WriteValue
The following commands from AutoIT i can use for these to be replaced:

AutoIT Commands:

  • @OSVersion
  • DriveMapAdd andDriveMapDel
  • Run(@ComSpec & " /c " &
  • RegWrite
The InGroup version i could use the one from this topic: http://www.autoitscript.com/forum/index.php?showtopic=37378

But is the best solution to use?

And last but not least, the Printer commands.

Could anyone help me to create loginscripts in AutoIT, so i can replace KIX32 with AutoIT scripts?

Edited by Iznogoud

Share this post


Link to post
Share on other sites



It might help if you werer a little more specific in your description of what you want to do. I know I at least have never heard of KIX32.


[center][/center]Working on the next big thing.Currently Playing: Halo 4, League of LegendsXBL GT: iRememberYhslaw

Share this post


Link to post
Share on other sites

It's actually KixTart, Kix32 is the executable. I would be replacing the Kix scripts that I support if Autoit had the equivalent of ingroup, the AD hierarchy is extremely complicated for some of the clients and AutoIT could do it but it would double the amount of code needed.

Share this post


Link to post
Share on other sites

#5 ·  Posted (edited)

The other option i have is using AutoIT as a front end to create the splash window with progress and running kix scripts hidden on the background. But i hoped it was possible to do it all in AutoIT.

Kix32 Commands:

  • @PRODUCTTYPE
  • USE
  • AddPrinterConnection
  • InGroup
  • SetDefaultPrinter
  • Shell %COMSPEC%....
  • WriteValue

Kix32 Commands Explained:

  • Used in an IF statement to check if the OS is Windows XP and not a Windows 2003
  • Used to create/map network drives
  • Check if the printer has been installed, if not add the printer.
  • Check if the user is member of a group, if so execute some random command
  • Setting the default printer
  • Running a DOS command
  • Reading and Writing of the registry
Edited by Iznogoud

Share this post


Link to post
Share on other sites

#6 ·  Posted (edited)

@All

My 2 cents.

I still use KIX :)

And was not planning on replacing it yet for the very same reason mentioned by the OP.

But to overcome your InGroup. You can symply use the InGroup.exe from MS which they supply to use in VBScript.

Regards,

ptrex

Edited by ptrex

Share this post


Link to post
Share on other sites

The AD group stuff can be overcome with the _ADIsMemberOf function from the AD functions script by Jonthan Clelland.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0