taitt2

I generally use something like the following subroutine: Imports ActiveDs . . . 'sub get_ntfs_acl(ByVal path As String) ' Dim sdutil As New ADsSecurityUtility Dim sd As SecurityDescriptor = sdutil.GetSecurityDescriptor(path, ADS_PATHTYPE_ENUM.ADS_PATH_FILE, ADS_SD_FORMAT_ENUM.ADS_SD_FORMAT_IID) Dim acl As AccessControlList = sd.DiscretionaryAcl For Each ace As AccessControlEntry In acl console.writeline(ace.Trustee) console.writeline(ace.Flags) console.writeline(ace.AccessMask) console.writeline(ace.AceFlags) console.writeline(ace.AceType) console.writeline(ace.InheritedObjectType) console.writeline(ace.ObjectType) console.writeline() Next ace End sub you have to use the ADSI interop, but it's a lot easer than the alternitives. you will have to translate the AccessMask rights. I usually set it manualy, then look at what the value translates into. I know this isn't a lot of detail. but if you search MSDN for security descriptors, you can get some more info. It's the same technique to read Active Directory Dacls, but you need a different way to creat the security descriptor object.

Has anyone translated this to Winpe from Barts pe?

Hmm, I guess that I will have to look more deeply into what is causing the errors then. Might be something that my net exe program is calling. Thanks

thats what I am afreaid of, I am just hoping that someone might have found a way around it.

ok, This might seam weird, but does anyone know how to get .net up and running enough so that you can actually run vb.net executables during the cmdlines section? I have been able to install it, but it seems to be missing something during this stage (I am hoping it might be a service that I can turn on or something). Has anyone had any luck running .net stuff from within Unattended? Joe.

Thanks that was it. I thought it must be some typo I couldn't see (it always worked before). Supprising how having Command and not Commands can really mess things up.

Thanks, I tried using the Pause things before going with the MD command. I switched because I thought that mabey the file was processing, but not interactively. I will give it another try though (like the idea of the two pauses). Sorry about not useing , I forgot

ok, I am willing to admit defeat. I am trying to get a XP RIS install to process the CMDLINES.txt file and no matter what I try, it dosn't seam to run it. I am running RIS from a 2003 server and the instalation of XP installs. it appears to copy the files from the $OEM$\$$ folder to the system 32 folder just like it should, but it dosn't seam to process the CMDLINES.TXT file that is located at the root of the $OEM$ folder. Does anyone have any suggestions? here are some of the configuration files: Directory Structure: \\xload1\REMINST\Setup\English\Images\WINDOWS_xp\i386 XP files \\xload1\REMINST\Setup\English\Images\WINDOWS_xp\i386\templates RIS SIF \\xload1\REMINST\Setup\English\Images\WINDOWS_xp\$OEM$ Oem files (The docs still say to put the OEM at the same level as the i386 for ris, and I even tried it in the i386 folder like you do for non ris). The cmdlines.txt file is located at the root of the $OEM$ folder and is as fallows ________________________________________________________ [COMMAND] "md c:\fred" ".\regedt32.exe /s .\AutoLogon.reg" _________________________________________________________ the Autologon.reg folder is also located at the root of the OEM. I put the MD C:\fred to tray and make a folder to prove it was actually seeing the cmdlines.txt file (no luck). Here is the SIF file that I am processing: ________________________________________________________________ ;SetupMgrTag [Data] floppyless="1" msdosinitiated="1" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%" OriTyp="4" LocalSourceOnCD=1 [setupData] OsLoadOptions="/noguiboot /fastdetect" setupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [unattended] OemSkipEula=Yes OEMPREINSTALL = Yes TargetPath=\WINDOWS FileSystem=LeaveAlone ExtendOEMPartition=0 InstallFilesPath="\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%" LegacyNIC=1 [GuiUnattended] OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=%TIMEZONE% AdminPassword=(Deleted) EncryptedAdminPassword=no [userData] ProductID=(Deleted) FullName="Current User" OrgName="Orgname" ComputerName=%MACHINENAME% [Display] BitsPerPel=24 Xresolution=1024 YResolution=768 [identification] JoinDomain=%MACHINEDOMAIN% DoOldStyleDomainJoin=Yes [Networking] InstallDefaultComponents=No [NetAdapters] Adapter1=params.Adapter1 [params.Adapter1] INFID=* [NetClients] MS_MSClient=params.MS_MSClient [NetServices] MS_SERVER=params.MS_SERVER [NetProtocols] MS_TCPIP=params.MS_TCPIP [params.MS_TCPIP] DNS=No UseDomainNameDevolution=No EnableLMHosts=Yes AdapterSections=params.MS_TCPIP.Adapter1 [RemoteInstall] Repartition=Yes UseWholeDisk=Yes [OSChooser] Description="Windows XP Profesional ver 8.1 - Select Installation" Help="This will install Windows XP Profesional Select with configuration." LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType=Flat Version="5.1 (0)" _______________________________________________________________ the files in the $OEM$\$$ folder copies correctly, so that should mean that the preinstall setting are correct. but it refuses to process the cmdlines.txt file. I suspect that it is some stupid typo that I am just not able to see. but I am at the stage of willing to beg for insight.