Jump to content

IcemanND

Patron
  • Posts

    3,252
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by IcemanND

  1. It doesn't like the default unicode encoding of out-file. It also appears to have a problem with the file being "open" at the same time you are writing to it, though since the default startnet.cmd file only has the one wpeinit line it may not make a difference to you.

    Personally I would replace this:

    Get-Content $cmd | Where {$_ -ne "wpeinit"} | Out-File $cmd
    Write-Output "@echo off" >> $cmd
    Write-Output "echo Inititalizing WinPE ..." >> $cmd
    Write-Output "wpeinit" >> $cmd
    Write-Output "echo Initialized!" >> $cmd
    Write-Output "echo Connecting to Image Server ..." >> $cmd
    Write-Output "net use Z: `"\\SRHS-SUP-FS\Desktop Support\Images`"" >> $cmd
    Write-Output "echo Connected!" >> $cmd
    Write-Output "cd /d Z:\" >> $cmd
    Write-Output "echo Launching GUI Interface ..." >> $cmd
    Write-Output "index.hta" >> $cmd

    With something like this:

    $startnet = Get-Content $cmd | Where {$_ -ne "wpeinit"}
    $startnet += "@echo off"
    $startnet += "echo Inititalizing WinPE ..."
    $startnet += "wpeinit"
    $startnet += "echo Initialized!"
    $startnet += "echo Connecting to Image Server ..."
    $startnet += "net use Z: `"\\SRHS-SUP-FS\Desktop Support\Images`""
    $startnet += "echo Connected!"
    $startnet += "cd /d Z:\"
    $startnet += "echo Launching GUI Interface ..."
    $startnet += "index.hta"
    Out-File -filepath $cmd -InputObject $startnet -Encoding ASCII

  2. I assume you tired the above without success in Vista? I no longer run any vista systems so I have no way to check or test.

    Alternatively you can open gpedit.msc and browse to the same setting:

    Computer Configuration\Windows Settings\Security Settings\Local

    Policies\User Rights Assignment

    As far as I know this is in every NT based OS.

  3. I don't know if Dragon Naturally Speaking can take an audio file as input but you could loop the speaker output to the mic. It does a fairly good job of recognition, though you might end up missing some punctuation.

  4. I removed your attached file for you since you left you product key in it.

    in the AutoLogon seciton you are missing the <Enabled> value.



    <AutoLogon>
    <Password>
    <Value>UABhAHMAcwB3AG8AcgBkAsdfsdfsdfCEAUABhAHMAcwB3AG8AcgBkAA==</Value>
    <PlainText>false</PlainText>
    </Password>
    <Enabled>true</Enabled>
    <LogonCount>2</LogonCount>
    <Username>Administrator</Username>
    </AutoLogon>

  5. Do you pre-create the computer accounts in AD? Otherwise with your answer file it will by default try and create the computer account in the default Computers OU which in most places I have been has been restricted to domain admins only. If you supply the OU or pre-create the computer objects in the correct location with the correct name anyone with rights to join a computer to the domain should be able to.

  6. If all of the machines are going into the same OU you won't have a problem, or if you have a staging OU and then move them from there to their permanent OU. Otherwise if you change the <machineobjectOU> value before the machine attempts to do the join you'll be fine. I do this right after applying the image to the machine before rebooting. If you are using Ghost version 11.x you should be able to do the same thing.

            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Identification>
    <Credentials>
    <Domain>contoso.com</Domain>
    <Password>joinpassword</Password>
    <Username>joinaccount</Username>
    </Credentials>
    <JoinDomain>contoso.com</JoinDomain>
    <MachineObjectOU>OU=Computers,OU=finance,DC=contoso,DC=com</MachineObjectOU>
    </Identification> </component>

  7. Use the system image manager, manually creating the Win7 unattend.xml answer file is near impossible. Just use the install.wim from your install media as the reference image when asked.

    There is a good blog here with most of the info you would be looking for.

    For the domain join you either need to pre-create the computer account in AD and the provided account has rights to join, or supply the OU the machine will be created in and the provided account has rights to create the object and join to it.

  8. In the black bar above any forum page where it says "Logged in as jclarkw" you can click on your user name and select "Messenger", or to the right of that if you have a message there should be a link to the messenger.

    In the messages page in the folders list the the New folder will have anything you have not read and the "My Conversations" folder will have any messages you have read or sent.

  9. you could script it, so that you run the script and check the existing version and if older than what you are deploying copy the installer from a network share to the machine and install.

    Or you push the current version to everyone, then I believe you can use the upgrade option in the advanced software deployment in GPOs to perform future maintenance.

    And in the meantime look into and invest in SCCM.

×
×
  • Create New...