Jump to content

When will the Anniversary Update appear on the VLSC?

FragglePete

By FragglePete
in Windows 10

 Share

Recommended Posts

FragglePete

FragglePete

Posted
Posted

We're sitting on our hands abit, but wondering if we should.....

 

The question is.... when will the anniversary update appear on the Volume License Service Centre ? Will it be on the actual launch date? Or much later? Judging by the fact the 1511 update was released July '15 and didn't appear as an iso for enterprise until November.

 

We're ready to roll out Windows 10. Group Policies all set up, etc. I've even got an image ready to roll that is full patched and tested.

 

We've done all our 'little' jobs, but haven't started to deploy yet.... so, the question is, shall we just go ahead with what we got or is it worth waiting? We reckon we can have the entire site done in 2 weeks (approx 700 devices).

 

Thoughts?

 

Pete

jmak

jmak

Posted
Posted
We're sitting on our hands abit, but wondering if we should.....

 

The question is.... when will the anniversary update appear on the Volume License Service Centre ? Will it be on the actual launch date? Or much later? Judging by the fact the 1511 update was released July '15 and didn't appear as an iso for enterprise until November.

 

We're ready to roll out Windows 10. Group Policies all set up, etc. I've even got an image ready to roll that is full patched and tested.

 

We've done all our 'little' jobs, but haven't started to deploy yet.... so, the question is, shall we just go ahead with what we got or is it worth waiting? We reckon we can have the entire site done in 2 weeks (approx 700 devices).

 

Thoughts?

 

Pete

 

The 1511 version didn't arrive until November because it was the November release. I'm pretty sure the original version arrived promptly, although couldn't give you an exact day....

  • Thanks 1
DJ-1701

DJ-1701

Posted
Posted

The original Windows 10 release ISO was on VLSC from August 1st, but some VLSC accounts did not have the item added automatically which required Microsoft to manually add it, and some to call up from the product keys.

 

The November release took about 1 month to appear from the time the update was released for an integrated ISO to be available on VLSC, even then they left the description when importing it into MDT as 'Technical Preview'. :rolleyes:

  • Thanks 1
DJ-1701

DJ-1701

Posted
Posted
IT'S ON THERE NOW!!! :D

 

Secondary VLSC user confirmation.

Windows 10 Education, Version 1607 (Updated Jul '16) 64 Bit English available when downloading. :D

mullet_man

mullet_man

Posted
Posted
Just building the base image now ready to capture. Seems ok so far. Notice that already there is an Update for this version already!!!!

 

Pete

 

Me too, wasn't expecting it today so it's good that I can make a start on my image.

 

Does anyone know if we need to update MDT or WAIK to capture an image of this?

gshaw

gshaw

Posted
Posted

A bit of quick testing looks promising - a new user profile on a domained machine gets in within 30 seconds rather than previous miserable attempts with 1511 that took 1min30s or above.

 

That's on a VM running on HDD so may even better on an SSD machine :)

FragglePete

FragglePete

Posted
  • Author
Posted

Initial logon times for us seem a bit longer, but nothing I'm too worried about. Couple of extra Apps being installed that weren't there before (Microsoft.Maps being one of them) so I'll need to tweak my MDT Scripts but so far looks ok.

 

Pete

FragglePete

FragglePete

Posted
  • Author
Posted (edited)
Initial logon times for us seem a bit longer, but nothing I'm too worried about. Couple of extra Apps being installed that weren't there before (Microsoft.Maps being one of them) so I'll need to tweak my MDT Scripts but so far looks ok.

 

Pete

 

Interesting. Just tweaked my script which removed Maps and after another rebuild it has reduced the logon time by nearly half. (Approx 35 secs).

 

Promising.

 

Pete

Edited by FragglePete
gshaw

gshaw

Posted
Posted
Interesting. Just tweaked my script which removed Maps and after another rebuild it has reduced the logon time by nearly half. (Approx 35 secs).

 

Promising.

 

Pete

@FragglePete any chance I could be cheeky and ask for a copy of your script? We have an app removal script on our 1511 build but would be good to double check it against the one you're using. Logon times for me were similar to your findings :)

FragglePete

FragglePete

Posted
  • Author
Posted
@FragglePete any chance I could be cheeky and ask for a copy of your script? We have an app removal script on our 1511 build but would be good to double check it against the one you're using. Logon times for me were similar to your findings :)

 

We're using the PS Script below during the last part of the Task Sequence. It looks for a RemoveApps.xml file first, if it's not there it'll create it with all the Apps installed and remove them all. If the file is there, it will then remove what is in the list so you can edit it as necessary.

 

Pete

 

 

# ***************************************************************************
# 
# File:      RemoveApps.ps1
# 
# Version:   1.2 
# 
# Author:    Michael Niehaus 
#
# Purpose:   Removes some or all of the in-box apps on Windows 8, Windows 8.1,
#            or Windows 10 systems.  The script supports both offline and
#            online removal.  By default it will remove all apps, but you can
#            provide a separate RemoveApps.xml file with a list of apps that
#            you want to instead remove.  If this file doesn't exist, the
#            script will recreate one in the log or temp folder, so you can
#            run the script once, grab the file, make whatever changes you
#            want, then put the file alongside the script and it will remove
#            only the apps you specified.
#
# Usage:     This script can be added into any MDT or ConfigMgr task sequences.
#            It has a few dependencies:
#              1.  For offline use in Windows PE, the .NET Framework, 
#                  PowerShell, DISM Cmdlets, and Storage cmdlets must be 
#                  included in the boot image.
#              2.  Script execution must be enabled, e.g. "Set-ExecutionPolicy
#                  Bypass".  This can be done via a separate task sequence 
#                  step if needed, see [url]http://blogs.technet.com/mniehaus[/url] for
#                  more information.
#
# ------------- DISCLAIMER -------------------------------------------------
# This script code is provided as is with no guarantee or waranty concerning
# the usability or impact on systems and may be used, distributed, and
# modified in any way provided the parties agree and acknowledge the 
# Microsoft or Microsoft Partners have neither accountabilty or 
# responsibility for results produced by use of this script.
#
# Microsoft will not provide any support through any means.
# ------------- DISCLAIMER -------------------------------------------------
#
# ***************************************************************************

# ---------------------------------------------------------------------------
# Initialization
# ---------------------------------------------------------------------------
if ($env:SYSTEMDRIVE -eq "X:")
{
 $script:Offline = $true
 # Find Windows
 $drives = get-volume | ? {-not [string]::IsNullOrWhiteSpace($_.DriveLetter) } | ? {$_.DriveType -eq 'Fixed'} | ? {$_.DriveLetter -ne 'X'}
 $drives | ? { Test-Path "$($_.DriveLetter):\Windows\System32"} | % { $script:OfflinePath = "$($_.DriveLetter):" }
 Write-Verbose "Eligible offline drive found: $script:OfflinePath"
}
else
{
 Write-Verbose "Running in the full OS."
 $script:Offline = $false
}

# ---------------------------------------------------------------------------
# Get-LogDir:  Return the location for logs and output files
# ---------------------------------------------------------------------------
function Get-LogDir
{
 try
 {
   $ts = New-Object -ComObject Microsoft.SMS.TSEnvironment -ErrorAction Stop
   if ($ts.Value("LogPath") -ne "")
   {
     $logDir = $ts.Value("LogPath")
   }
   else
   {
     $logDir = $ts.Value("_SMSTSLogPath")
   }
 }
 catch
 {
   $logDir = $env:TEMP
 }
 return $logDir
}
# ---------------------------------------------------------------------------
# Get-AppList:  Return the list of apps to be removed
# ---------------------------------------------------------------------------
function Get-AppList
{
 begin
 {
   # Look for a config file.
   $configFile = "$PSScriptRoot\RemoveApps.xml"
   if (Test-Path -Path $configFile)
   {
     # Read the list
     Write-Verbose "Reading list of apps from $configFile"
     $list = Get-Content $configFile
   }
   else
   {
     # No list? Build one with all apps.
     Write-Verbose "Building list of provisioned apps"
     $list = @()
     if ($script:Offline)
     {
       Get-AppxProvisionedPackage -Path $script:OfflinePath | % { $list += $_.DisplayName }
     }
     else
     {
       Get-AppxProvisionedPackage -Online | % { $list += $_.DisplayName }
     }
     # Write the list to the log path
     $logDir = Get-LogDir
     $configFile = "$logDir\RemoveApps.xml"
     $list | Set-Content $configFile
     Write-Information "Wrote list of apps to $logDir\RemoveApps.xml, edit and place in the same folder as the script to use that list for future script executions"
   }
   Write-Information "Apps selected for removal: $list.Count"
 }
 process
 {
   $list
 }
}
# ---------------------------------------------------------------------------
# Remove-App:  Remove the specified app (online or offline)
# ---------------------------------------------------------------------------
function Remove-App
{
 [CmdletBinding()]
 param (
       [parameter(Mandatory=$true,ValueFromPipeline=$true)]
       [string] $appName
 )
 begin
 {
   # Determine offline or online
   if ($script:Offline)
   {
     $script:Provisioned = Get-AppxProvisionedPackage -Path $script:OfflinePath
   }
   else
   {
     $script:Provisioned = Get-AppxProvisionedPackage -Online
     $script:AppxPackages = Get-AppxPackage
   }
 }
 process
 {
   $app = $_
   # Remove the provisioned package
   Write-Information "Removing provisioned package $_"
   $current = $script:Provisioned | ? { $_.DisplayName -eq $app }
   if ($current)
   {
     if ($script:Offline)
     {
       $a = Remove-AppxProvisionedPackage -Path $script:OfflinePath -PackageName $current.PackageName
     }
     else
     {
       $a = Remove-AppxProvisionedPackage -Online -PackageName $current.PackageName
     }
   }
   else
   {
     Write-Warning "Unable to find provisioned package $_"
   }
   # If online, remove installed apps too
   if (-not $script:Offline)
   {
     Write-Information "Removing installed package $_"
     $current = $script:AppxPackages | ? {$_.Name -eq $app }
     if ($current)
     {
       $current | Remove-AppxPackage
     }
     else
     {
       Write-Warning "Unable to find installed app $_"
     }
   }
 }
}

# ---------------------------------------------------------------------------
# Main logic
# ---------------------------------------------------------------------------
$logDir = Get-LogDir
Start-Transcript "$logDir\RemoveApps.log"
Get-AppList | Remove-App
Stop-Transcript


[font=Lucida Console][size=1][color=#0000ff][font=Lucida Console][size=1][color=#0000ff][font=Lucida Console][size=1][color=#0000ff]
[/color][/size][/font][/color][/size][/font][/color][/size][/font]

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...