[Unattended] unattended

[Xalo Rous]

On http://unattended.sourceforge.net/step-by-step.php, it says:

 

Windows server

Create the SMB file share:

c:\> net share install=c:\path\to\unattended\install
c:\> cacls c:\path\to\unattended\install /T /E /G:guest
c:\> net user guest /ACTIVE:YES /DOMAIN

the cacls command needs the following syntax: (excerpt from cacls /?)
   /G user:perm  Grant specified user access rights.
                 Perm can be: R  Read
                              W  Write
                              C  Change (write)
                              F  Full control
I don't know which permissions this share needs but I assume it would be either Read or Change.  In which case it should say,

c:\> cacls c:\path\to\unattended\install /T /E /G guest:R

-or-

c:\> cacls c:\path\to\unattended\install /T /E /G guest:C

 

Also, most Windows 'best practices' rename and/or disable the 'guest' account, so this might not be the best account name to use as an example.  Especially since that third command looks like it is either creating or activating the guest account.  Which would be a security violation on many networks.

 

Therefore, for security reasons, it would be best to use a different account name for the third command (and the second one of course).  E.g.:

c:\> net user installer /add /DOMAIN

c:\> net share install=c:\path\to\unattended\install
c:\> cacls c:\path\to\unattended\install /T /E /G installer:R

• [note: this requires the right to add users to the domain/computer]
• [note2: leave out /DOMAIN to create a local account] 

More about Net Use here:  http://support.microsoft.com/?scid=251394

More about cacls.exe here: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/cacls.mspx

 

Having said all this, almost anyone who would be creating an unattended install could create a shared install point, restricted to a single, purpose-created user account.  The main reason I wrote in the first place is the cacls issue, it would not work as it was.