Adding shutdown=1 to the Boot Options for the deploy option does not work. Tested on 3 different devices.

Has anyone used these models FOG yet? We’re supposed to be getting these soon and I just wanted to know if there are any known issues. Didn’t see these models on the compatibility list.

@Tom-Elliott said in New PXE menu entry: Deploy Image & Shutdown:

@Avaryan Then something wasn’t done correctly. Did you have exactly shutdown=1? Code to validate is literally:
[[ $shutdown -eq 1 ]] && poweroff || reboot -f

This is exactly what I have:
http://puu.sh/vT05Q/eae7a8eadc.png

Did not work. It was an unregistered host. Haven’t tried with a registered one.

FOG 1.4.0 Revision 6069.

edit: Deploying image to a different model now. Device is registered (although that shouldn’t matter?). ETA 15 minutes.

@Tom-Elliott said in New PXE menu entry: Deploy Image & Shutdown:

@george1421 It definitely is the easiest way, but if it’s specific to “quick imaging” goto:
FOG Configuration Page->iPXE Menu Configuration->fog.deployimage
In Boot Options: add: shutdown=1

If you want it for ALL tasks (will not impact debug of course):
FOG Configuration Page->FOG Settings->General Settings->FOG_KERNEL_ARGS and add: shutdown=1

I just tried this and it did not work. Still booted to Windows after imaging.

Testing something. I’ll let you know in about 15 minutes if it worked.
edit: Didn’t work.

So, the overall objective here, is it just to get Windows updated? Does it have it be offline using wsusoffline?

There are PowerShell modules for Windows Update that may be able to trigger updates.

How did you get those values there?

Based on a couple minutes of research, I don’t think you can run UpdateInstaller.exe silently. So this is likely just not going to work.
http://www.wsusoffline.net/docs/

@plegrand said in snapin and batch script:

But for the moment my problem is : how mount a samba share with snapin which is usable by administrator user

What version of Windows would this Snapin be run on?

@plegrand said in snapin and batch script:

@Avaryan As you can see , i need to mount the share and execute a command which is inside this share…
Then i thin it’s not possible ?

Should be possible.

$Username = "samba\administrator"
$Password = "my'password" | ConvertTo-SecureString -AsPlainText -Force
$Credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Username, $Password

New-PSDrive -Name "Samba" -PSProvider FileSystem -Root '\\samba\wsus$' -Credential $Credential
$UpdateInstaller = Get-ChildItem -Path "Samba:\wsusoffline\client\" | Where-Object -Property Name -EQ "UpdateInstaller.exe"
Start-Process -FilePath $UpdateInstaller.FullName -Wait
Remove-PSDrive -Name "Samba"

Depending on how large the UpdateInstaller.exe is and how many devices you are doing at once, it might be better to have this copy it over and run locally.

@plegrand said in snapin and batch script:

@Avaryan it’s for use WsusOffline which is installed on a samba share \samba\wsus
then i need to mount the wsus share , launch a command (wsus command) dnd then umount share.

Ok. That should be possible since the local users don’t need to access the mount. Should be pretty easy in PowerShell. I don’t know how to do it other ways, lol.

$Username = "Domain\User"
$Password = "Password" | ConvertTo-SecureString -AsPlainText -Force
$Credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Username, $Password
# Add share.
New-PSDrive -Name "MyShare" -PSProvider FileSystem -Root \\ShareName\ -Credential $Credential

# Do something...
# More somethings...

Remove-PSDrive -Name "MyShare"

@plegrand said in snapin and batch script:

@Tom-Elliott the user who established the mount => You means system user ?

FOG runs the snapin as the local SYSTEM account. So the drive is getting mounted under that account and not under any useable user.

Yes, the result was the same via PowerShell. I just tested it.

Do you need users to be able to access the drive? Or do you just need to mount the drive to do some action and then unmount the drive?

Assuming you’re deploying to a Windows PC.

Perhaps convert to PowerShell to mount/unmount the network share? It might work better.

Example for mounting/unmounting shares.

$Username = "Domain\Username"
$Password = "Password" | ConvertTo-SecureString -AsPlainText -Force
$Credential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Username, $Password
# Add share.
New-PSDrive -Name "MyShare" -PSProvider FileSystem -Root \\ShareName\SomeFolder -Credential $Credential
# Remove share.
Remove-PSDrive -Name "MyShare"

I had that happen before when one of the repo’s were being blocked by our network filter.

Just for reference. I have Dell OptiPlex 7040’s and they’ve worked fine from FOG version 1.2.0 and higher.

I believe I may have had to change some BIOS settings before deploying to them the first time.

edit: Imaged 7040 with both Windows 7 and Windows 10. I’ll set one up and check the BIOS settings.
edit2: Here are the relevant BIOS settings on the OptiPlex 7040 that I think I changed (like a year ago).

Under System Configuration:

• Integrated NIC
  – Uncheck “Enable UEFI Network Stack” (this might be default)
  – Select “Enabled w/PXE”
• SATA Operation
  – Select “RAID ON” (Default was either Disabled or AHCI)

I think that’s all I changed.

@abu.raju said in Add new standard user on windows 10:

@x23piracy I am retentively new to FOG. I would appreciate if you guys show me how to do this using snapin. Thanks all of you!

NOTE: This is not working for me. When I run the file locally, it creates the user account. When I attempt running from FOG it does not. I can get it to do other things, but not create the account.
Ok, here is how I would do it.

First, create a new PowerShell script. Open up PowerShell ISE and copy/paste the following. Replace with your information.

$Name = "TestUser"
$FullName = "Test User"
$Password = "Password123" | ConvertTo-SecureString -AsPlainText -Force
$Description = "A standard user account."

New-LocalUser -Name $Name -FullName $FullName -Password $Password -Description $Description

Save it. Name it whatever you want.

Open your browser. Go to your FOG server page. Click on the Snapins icon, then click Create New Snapin. Fill in the details. Before sure to select the PowerShell option from the Snapin Template. Click the Choose File button to pick your PowerShell script and upload it. Then click the Add button at the bottom (not in screenshot).

After that you’ll need to assign the snapin to your host(s) and when you image it will (by default) run the snapin after deployment.

@abu.raju said in Add new standard user on windows 10:

@x23piracy I am retentively new to FOG. I would appreciate if you guys show me how to do this using snapin. Thanks all of you!

Ok. Give me a little bit. I want to write it up real fast and make sure it actually works.

@x23piracy said in Add new standard user on windows 10:

FYI, Powershell command/script can also be used as a snapin.

Regards X23

I had intended to say this in previous post, but the fire drill rushed me. lol

@abu.raju said in Add new standard user on windows 10:

Hi!
just searching to find a solution to add a new user on PC during or after we deploy the image. Is it possible to remove and add a new standard user on a workgroup computer during or after image deployment? If yes, how we can accomplish that. I appreciate all suggestion and help.

You can create a new local user with a simple PowerShell command:

New-LocalUser

Something like this may work, although I haven’t tested it.

$Name = "TestUser"
$FullName = "Test User"
$Password = "Password123" | ConvertTo-SecureString -AsPlainText -Force

New-LocalUser -Name $Name -FullName $FullName -Password $Password -AccountNeverExpires -PasswordNeverExpires

For more details open a PowerShell window and type

Get-Help New-LocalUser -ShowWindow

Or read through this:

Synopsis
    Creates a local user account.

Description
    The New-LocalUser cmdlet creates a local user account. This cmdlet creates a local user account or a local user account that is connected to a Microsoft account.


Parameters
    -AccountExpires <DateTime>
        Specifies when the user account expires. To obtain a DateTime object, use the Get-Date cmdlet. If you do not specify this parameter, the account does not expire.

        Required?                    false
        Position?                    named
        Default value                None
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -AccountNeverExpires <SwitchParameter>
        Indicates that the account does not expire.

        Required?                    false
        Position?                    named
        Default value                False
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -Confirm <SwitchParameter>
        Prompts you for confirmation before running the cmdlet.

        Required?                    false
        Position?                    named
        Default value                False
        Accept pipeline input?       False
        Accept wildcard characters?  false

    -Description <String>
        Specifies a comment for the user account. The maximum length is 48 characters.

        Required?                    false
        Position?                    named
        Default value                None
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -Disabled <SwitchParameter>
        Indicates that this cmdlet creates the user account as disabled.

        Required?                    false
        Position?                    named
        Default value                False
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -FullName <String>
        Specifies the full name for the user account. The full name differs from the user name of the user account.

        Required?                    false
        Position?                    named
        Default value                None
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -Name <String>
        Specifies the user name for the user account.
        

        Required?                    true
        Position?                    0
        Default value                None
        Accept pipeline input?       True (ByPropertyName, ByValue)
        Accept wildcard characters?  false

    -NoPassword <SwitchParameter>
        Indicates that the user account does not have a password.

        Required?                    true
        Position?                    named
        Default value                False
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -Password <SecureString>
        Specifies a password for the user account. You can use `Read-Host -GetCredential`, Get-Credential, or ConvertTo-SecureString to create a SecureString object for the password.
        

        Required?                    true
        Position?                    named
        Default value                None
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -PasswordNeverExpires <SwitchParameter>
        Indicates whether the password expires.

        Required?                    false
        Position?                    named
        Default value                False
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -UserMayNotChangePassword <SwitchParameter>
        Indicates that the user cannot change the password on the user account.

        Required?                    false
        Position?                    named
        Default value                False
        Accept pipeline input?       True (ByPropertyName)
        Accept wildcard characters?  false

    -WhatIf <SwitchParameter>
        Shows what would happen if the cmdlet runs. The cmdlet is not run.

        Required?                    false
        Position?                    named
        Default value                False
        Accept pipeline input?       False
        Accept wildcard characters?  false



Syntax
    New-LocalUser [-Name] <String> [-AccountExpires <DateTime>] [-AccountNeverExpires ] [-Confirm ] [-Description <String>] [-Disabled ] [-FullName <String>] -NoPassword  [-UserMayNotChangePassword ] [-WhatIf ] [<CommonParameters>]

    New-LocalUser [-Name] <String> [-AccountExpires <DateTime>] [-AccountNeverExpires ] [-Confirm ] [-Description <String>] [-Disabled ] [-FullName <String>] -Password <SecureString> [-PasswordNeverExpires ] [-UserMayNotChangePassword ] [-WhatIf ] [<CommonParameters>]


Inputs
    System.String, System.DateTime, System.Boolean, System.Security.SecureString
    You can pipe a string, a DateTime object, a Boolean value, or a secure string to this cmdlet.

Outputs
    System.Management.Automation.SecurityAccountsManager.LocalUser
    This cmdlet returns a LocalUser object. This object provides information about the user account.

Notes
    * A user name cannot be identical to any other user name or group name on the computer. A user name cannot consist only of periods (.) or spaces. A user name can contain up to 20 uppercase characters or lowercase characters. A user name cannot contain the following characters:
    

Examples
    Example 1: Create a user account
    PS C:\>New-LocalUser -Name "User02" -Description "Description of this account." -NoPassword
    Name    Enabled  Description
    ----    -------  -----------
    User02  True     Description of this account.
    
    This command creates a local user account. The command does not specify the AccountExpires parameter. Therefore, the account does not expire.
    Example 2: Create a user account that has a password
    PS C:\>$Password = Read-Host -AsSecureString
    PS C:\> New-LocalUser "User03" -Password $Password -FullName "Third User" -Description "Description of this account."
    Name    Enabled  Description
    ----    -------  -----------
    User03  True     Description of this account.
    
    The first command prompts you for a password by using the Read-Host cmdlet. The command stores the password as a secure string in the $Password variable.

The second command creates a local user account by using the password stored in $Password. The command specifies a user name, full name, and description for the user account.
    Example 3: Create a user account that is connected to a Microsoft account
    PS C:\>New-LocalUser -Name "MicrosoftAccount\usr name@Outlook.com" -Description "Description of this account."
    
    This command creates a local user account that is connected to a Microsoft account. This example uses a placeholder value for the user name of an account at Outlook.com. Because the account is connected to a Microsoft account, do not specify a password.


RelatedLinks
    Online Version: http://go.microsoft.com/fwlink/?LinkId=822516
    Disable-LocalUser
    Enable-LocalUser
    Get-LocalUser
    Remove-LocalUser
    Rename-LocalUser
    Set-LocalUser

And… there’s a fire drill right now… I work in a school.