MartinByard

Download the language pack iso and the features on demand iso from the MS VL site, extract the ones I needed and added them to a package in SCCM (should be similar with MDT) and then had a run command line step in the task sequence that ran DISM and installed the features. The DISM step(s) are specifically: Dism /Online /Add-Package /PackagePath=".\Microsoft-Windows-Client-Language-Pack_x64_en-gb.cab" and Dism /Online /Add-Package /PackagePath:.\Microsoft-Windows-LanguageFeatures-Basic-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-OCR-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-Handwriting-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-TextToSpeech-en-gb-Package~31bf3856ad364e35~amd64~~.cab /PackagePath:.\Microsoft-Windows-LanguageFeatures-Speech-en-gb-Package~31bf3856ad364e35~amd64~~.cab

I had this - if its the same problem I had, then to fix it I needed to add the relevant language Feature's on Demand extra's (handwriting, speech etc.). This was most likely due to using the international iso to build the image, but specifing EN-GB as the language ...

Did you disable app store updates at all? If a store app manages to update that can break sysprep as well.

We had a similar issue on our new 2016 RDS farm (although only intermittently, it didn't effect everyone who tried to use it) and we think we finally managed to track it down to be something to do with the way the server was passing the RDP requests over http. Not sure if this is likely to be similar to what you're experiencing, given you're on 2019 .. but worth a mention. We seem to have fixed it by adding the below reg key to the effected machines (or at least the complaints seem to have stopped coming in). [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client] "RDGClientTransport"=dword:00000001

Have you checked to see if there are any BIOS updates available for the machines (bit of a long shot, but you never know ..)??

As far as I know, it is both an OS limit and a OneDrive client limit. Files on demand will only work on 1709 and above, but the version of OneDrive that comes with 1709 out of the box does not support it and needs to be updated (it will do this itself) before it is available.

I like Arthur's version, the only thing I might be tempted to add would be total RAM slots in the machine, and how many are used - for assistance in planning future upgrades ... which would give : $Results = @() $Computers = 'PC-001', 'PC-002' $Computers | ForEach-Object { $BIOS = Get-WmiObject Win32_BIOS -ComputerName $_ | Select-Object PSComputerName, SerialNumber, Version $CPU = Get-WmiObject Win32_Processor -ComputerName $_ | Select-Object Caption, Manufacturer, Name $RAM = (Get-WmiObject Win32_ComputerSystem -ComputerName $_).TotalPhysicalMemory/1GB -as [int] $colSlots = Get-WmiObject -class "Win32_PhysicalMemoryArray" -ComputerName $_ -namespace "root\CIMV2" $TotalSlots = $colSlots.MemoryDevices $colModules = Get-WMIObject -class "Win32_PhysicalMemory" -ComputerName $_ -namespace "root\CIMV2" $UsedSlots = 0 foreach ($objItem in $colModules) { $UsedSlots = $UsedSlots + 1 } $Specs = [PSCustomObject][Ordered]@{ 'Computer Name' = $BIOS.PSComputerName 'Serial Number' = $BIOS.SerialNumber 'BIOS Version' = $BIOS.Version 'CPU Caption' = $CPU.Caption 'CPU Manufacturer' = $CPU.Manufacturer.Replace('Genuine', '') 'CPU Model' = ($CPU.Name).Replace('Intel(R) ', '').Replace('(TM)', '') 'Total RAM (GB)' = $RAM 'Total RAM slots' = $TotalSlots 'Used RAM slots' = $UsedSlots } $Results += $Specs } $Results | Export-Csv -Path "$($env:USERPROFILE)\Desktop\ComputerDetails.csv" -NoClobber -Append -NoTypeInformation

Taking that one step further, this will loop until it's online and then pop up a message box saying when it came back online, then stop while ($true) { $ComputerName= "facebook" If (Test-Connection -ComputerName $ComputerName -Count 1 -Quiet) { $DT = get-date -format HH:mm Start-Job -ScriptBlock{[system.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms");[system.Windows.Forms.MessageBox]::Show("Computer $using:computername came back online at $using:DT", "Online Notification")} #Write-Host "$ComputerName is Online" break } else { #Write-Host "$ComputerName is offline" } Start-Sleep 10 }

I'd go with a scheduled task that links a GPO (already created for testing purposes ?) to an ou: Set-GPLink -Name TestGPO -Target "ou=MyOU,dc=contoso,dc=com" or Set-GPLink -Guid 77c5285d-952e-4559-94ef-a02f5c107799 -Target "ou=MyOU,dc=contoso,dc=com"

This works for me, what errors do you get when it runs? $user = Read-Host "Enter username to find Expiry date for:" Get-ADUser -Identity $user –Properties "DisplayName", "msDS-UserPasswordExpiryTimeComputed" | Select-Object -Property "Displayname",@{Name="ExpiryDate";Expression={[datetime]::FromFileTime($_."msDS-UserPasswordExpiryTimeComputed")}}

Hi ID-10T, From my experience being high on the revision numbers doesn't really matter, the problem would seem to be the install step referencing the wrong revision (as you suugest). For the most part i haven't had this issue, as my task sequence seems to pick up any changes made to the apps. Quick question to start - have you tried removing the app from the task sequence, and then re-adding it (as this should get it to reference the latest revision that you have)?

On the webpage I linked to, one of the first steps is to go to http://aka.ms/OfficeDBASignup and sign up to use DBA, and that runs through the process of creating your key.

Is wsat.onmicrosoft.com your managed domain ? as an example this is our commandline to get DBA working on a machine with O365 already installed. OPPTransition.exe -Tenant -Key -Domain leedsbeckett.onmicrosoft.com -Version 16 -NoInstall -NoUninstall -Verbose We initially followed this webpage https://sysadminedu.wordpress.com/2017/01/07/step-by-step-guide-to-deploying-office-365-pro-plus-with-device-based-activation-with-sccm/ to get things up and running (including the part about installing office as part of our base image, then just doing license activation in the task sequence).

I think this might be your problem (we've had something similar in the past when it was decided that a program needed to be in the start menu twice, once each for the different faculties that wanted to use it) .... Windows 10 is awkward and won't allow duplicates in the start menu, so given that there will already be a shortcut to Chrome (for example) that is there by default, when you try to add another (linking to your website for example) then windows will decide to only display one of them. To get around this we created a powershell script that launched the program (you could do it with a batch file as well), converted it to an exe and put a shortcut to that in the start menu.

This should do the trick: if(!(Test-Path "C:\Program Files\WindowsApps\Microsoft.Windows.Photos_2018.18 011.15918.0_x64__8wekyb3d8bbwe")){ &"\\(networkshare)\Windows Photos\InstallPhotosDISM.ps1" } (Test-Path "C:\Program Files\WindowsApps\Microsoft.Windows.Photos_2018.18 011.15918.0_x64__8wekyb3d8bbwe") returns true if the path exists, and false if it doesn't. The ! in front of it flips this so that it returns true if the path doesn't exist. Then simply call your other script and run it using the &.

The original Doom and/or Wolfenstein 3D maybe ?

You're thinking is right, SCCM uses the MAC address to identify machines (as well as the machine's SMBIOS GUID). if you were running a later version of SCCM (CB 1610 or above) then managing duplicate MAC addresses can be done in the console - but with 2012 you would need to edit the registry on the server. See https://www.systemcenterdudes.com/sccm-duplicate-hardware-identifiers/ for more details. We run a powershell script once the machine has been imaged and built to work around this (haven't got around to following the guide on the above webpage ourselves yet). Connect the machine to the network, wait for the SCCM client to be fully running and then run the below from an elevated powershell prompt and it should allow you to re-use the ethernet adaptor without picking up the wrong names # Ask to remove Ethernet dongle $wshell = New-Object -ComObject Wscript.Shell $continue = $wshell.Popup("Please disconnect the Ethernet adapter from the USB port",0,"Action Needed",0x1) if($continue -ne 1) {Exit 1} # Checks if Ethernet adapter was disconnected every 3s Do { Start-Sleep -s 3 } while ([boolean] (Get-NetIPAddress -InterfaceAlias *Ethernet* | where{$_.IPAddress -notlike "169.254.*.*"})) # Checks if the WiFi adapeter has a valid IP every 3s ### ACTION::: replace www.bing.com with the IP Address of ### your CM Management Point or a know IP address on your network Do { Start-Sleep -s 3 } while (!(Test-Connection -ComputerName -Quiet)) # Wait until device is associated to a site in Configuration Manager Do { Start-Sleep -s 3 Write-host "Checking if Device is associated with Configuration Manager Site" } while (![boolean] ($([WmiClass]"\\localhost\ROOT\ccm:SMS_Client").getassignedsite())) # Get Heartbeat and run Hardware Inventory $SMSCli = [WmiClass]"\\localhost\ROOT\ccm:SMS_Client" $SMSCli.triggerschedule("{00000000-0000-0000-0000-000000000003}") # Done Write-Host "All done! We will now recognize your device from its Internal Mac Address" -ForegroundColor black -BackgroundColor cyan # end Exit 0

It's a bit late, but when we wanted to test out Alexa we had to get a different VLAN set up that didn't route out through the proxy, otherwise it wouldn't work at all (it could join the normal wifi network we had, but couldn;t do anything with it).

Hi All, I'm Martin. I work at leeds Beckett University as an IT Development Specialist (fancy job title, but basically i'm one of our SCCM admins - I mainly deal with PC imaging, software packaging and deployment with some AD and group policy management etc. thrown in). I've been browsing these forums for a little while, finally registered now.