Deployment with fastest time from login to usable desktop

[wing5wong]

Hi there,

 

we are investigating windows 10 deployments, and so far have all our major software working on all our hardware.

What we would like now is the best way to ensure a fast logon. Our current situation would have 5-6 users per day logging on to a machine (1 each hour), with the possibility of them using new machines.

Im trying to add a package that removes the preinstalled apps, but no luck with that working from the TS yet (it works if i run it manually).

 

Are there any other modifications that can be made to improve logon time? (Remove the "Hi" screens, etc)

What is everyone else doing in regards to this - do you just accept the increased logon time?

 

Look forward to some opinions or thoughts

[wing5wong]

for reference, this i s the script i have as a package during the TS

powershell.exe -ExecutionPolicy Bypass -Command "cpi '%DEPLOYROOT%\Sources\Deployment Scripts\Remove Preinstalled Apps\remove_apps_win10.ps1' -destination C:\Windows\Temp; C:\Windows\Temp\remove_apps_win10.ps1; ri C:\Windows\temp\*.ps1 -Force"

<#     
    ************************************************************************************************************ 
    Purpose:    Remove built in apps specified in list 
    Pre-Reqs:    Windows 8.1 
    ************************************************************************************************************ 
#>

#--------------------------------------------------------------------------------------------------------------- 
# Main Routine 
#---------------------------------------------------------------------------------------------------------------

# Get log path. Will log to Task Sequence log folder if the script is running in a Task Sequence 
# Otherwise log to \windows\temp

try

{

$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment

$logPath = $tsenv.Value("LogPath")

}

catch

{

Write-Host "This script is not running in a task sequence"

$logPath = $env:windir + "\temp"

}

$logFile = "$logPath\$($myInvocation.MyCommand).log"

# Start logging

Start-Transcript $logFile

Write-Host "Logging to $logFile"

# List of Applications that will be removed

$AppsList = "Microsoft.3DBuilder", "Microsoft.BingFinance", "Microsoft.BingFoodAndDrink", "Microsoft.BingHealthAndFitness",
            "Microsoft.BingNews", "Microsoft.BingSports", "Microsoft.BingTravel", "Microsoft.BingWeather",
            "Microsoft.MicrosoftOfficeHub", "Microsoft.MicrosoftSolitaireCollection",
            "Microsoft.Office.OneNote", "Microsoft.Reader", "Microsoft.SkypeApp", "Microsoft.WindowsAlarms",
            "Microsoft.Windows.Photos", "Microsoft.WindowsCamera", "microsoft.windowscommunicationsapps",
            "Microsoft.WindowsMaps", "Microsoft.WindowsPhone", "Microsoft.XboxApp", "Microsoft.ZuneMusic", "Microsoft.ZuneVideo"

ForEach ($App in $AppsList)

{

$Packages = Get-AppxPackage | Where-Object {$_.Name -eq $App}

if ($Packages -ne $null)

{

      Write-Host "Removing Appx Package: $App"

      foreach ($Package in $Packages)

      {

      Remove-AppxPackage -package $Package.PackageFullName

      }

}

else

{

      Write-Host "Unable to find package: $App"

}

$ProvisionedPackage = Get-AppxProvisionedPackage -online | Where-Object {$_.displayName -eq $App}

if ($ProvisionedPackage -ne $null)

{

      Write-Host "Removing Appx Provisioned Package: $App"

      remove-AppxProvisionedPackage -online -packagename $ProvisionedPackage.PackageName

}

else

{

      Write-Host "Unable to find provisioned package: $App"

}

}

# Stop logging

Stop-Transcript

[jkovolski]

I came across this but haven't tested it.

http://blogs.technet.com/b/mniehaus/archive/2015/08/24/windows-10-mdt-2013-update-1-and-hideshell.aspx

​