Hello friends. I'm trying to create a script can be activated from ConfigMgr consol that will copy some folders and files to all users who been logged on the computer. The script is working fine if I'm running it manually from Powershell. If running the from ConfigMgr consol the "Script" function execute and complete but nothing happens. Just for testing I tried to add the lines below, then the console just keep saying creating job. I can see it copies the script to the target computer in the ScriptStore. ### Only for testing ### Add-Type -AssemblyName PresentationCore,PresentationFramework
$ButtonType = [System.Windows.MessageBoxButton]::OK
$MessageIcon = [System.Windows.MessageBoxImage]::Information
$MessageBody = "CUE Prod Installed!"
$MessageTitle = "Install Status"
$Result = [System.Windows.MessageBox]::Show($MessageBody,$MessageTitle,$ButtonType,$MessageIcon)   Add-Type -AssemblyName PresentationCore,PresentationFramework $UserFolder = Get-ChildItem -path "C:\Users\*" #$Folders = Get-ChildItem -Path $PSScriptRoot -Exclude "CUEPrint.lnk", "Install-CUEPrintProd.ps1", "Install-CUEPrintProdAllUsers.ps1" #$SourceLink = Get-Item -Path ($PSScriptRoot + "\CUEPrint.lnk") $Folders = Get-ChildItem -Path "\\XXX\s$\Powershell\Newsgate\Prod" -Exclude "CUEPrint.lnk", "Install-CUEPrintProd.ps1", "Install-CUEPrintProdAllUsers.ps1" $SourceLink = Get-Item -Path ("\\XXX\s$\Powershell\Newsgate\Prod" + "\CUEPrint.lnk") foreach ($file in $UserFolder) { Copy-Item $Folders -Destination $file'\Appdata\local' Copy-Item $SourceLink -Destination $file'\Desktop\' } Copy-Item $Folders -Destination 'C:\Users\Default\appdata\Local' Copy-Item $SourceLink -Destination 'C:\Users\Default\Desktop' ### Only for testing ### $ButtonType = [System.Windows.MessageBoxButton]::OK $MessageIcon = [System.Windows.MessageBoxImage]::Information $MessageBody = "CUE Prod Installed!" $MessageTitle = "Install Status" $Result = [System.Windows.MessageBox]::Show($MessageBody,$MessageTitle,$ButtonType,$MessageIcon) #Write-Host "Your choice is $Result"  

Hello, I just created a Windows 10 1803 WIM and imported into SCCM. I copied task sequencer from 1709 and changed OS-image.
When running task "Apply Operating System" I got error 0x80070002...

Report:
The user tries to release a source directory C:\_SMSTaskSequence\Packages\PS100091 that is either already released or we have not connected to it.
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ),
HRESULT=80070002 (applyos.cpp,509)
Http result: 404
SendResourceRequest() failed. 80190194
Download() failed. 80790794.
Installation of image 1 package PS100091 failed to complete..
The system cannot find the file specified. (Error: 80070002; Source: Windows)

The WIM workes on the other server so the WIM itself seems OK.
I have checked network access account, boundaries, the wim is deployed to my DP, remove wim from DP and distribute again
Checked "Data Access - Copy the content in this package to a package share on DP"... 
DP -> HTTP -> Allow clients to connect anonymusly

When I try running the old 1709-wim it works.

 

Hello, i am running sccm 1710 on windows 2016. My wsus with the system role for software update is also running on windows 2016. Under site settings for Software Update i activated the checkbox "include microsoft surface drivers...." and under products i select (see the screenshot)   My Surfaces are running 1709 (fall creators update) at the moment. Now, when i take a look under "All software updates" and search for "surface" i only see one firmware update:   But these updates are old. If i take a look on the MS Download Page, i found an MSI Driver Package from August, 10th. 2018. And all other updates are from 2017.  Why are these updates not visible in my console ? I cant believe, that there are no newer updates for wsus available... Any idea ?

I have a membership rule looking for clients equal to Operating system build 16299, it finds them, but it always includes 17134 builds too?    I cant figure out why!!!  Can anyone help?  

Hi  I'm trying to upgrade some surfaces pro 4 to 1803 using an OSD Inplace.  (this works on other machines BTW) I seen two devices with exactly the same HARDBLOCK in the logs. OEM01.inf and OEM02.inf I cannot find what these devices are anyone got any ideas where I can find out the information, I've scanned through the full scan and searched for a Hardblock without any results. Thanks for any assistance in advanced. Cheers   CompatData_2018_08_21_11_51_26_3_006f0018.xml

Hi Everyone, I am trying to get a simple application to install but it doesn't seem to work either running the TS from the desktop or during the image process. Its a normal MSI application but for some reason it just wont install by the looks of it using the system account. I tried running the application silently through CMD outside of SCCM under my logged in user account (which is an admin) but it just would not fire off.  I moved all the source files locally to the location c:\apps\Q-Pulse c:\apps\Q-Pulse> msiexec /i "Q-Pulse.msi" /qn When i load CMD as admin and run the same command above it works fine. Just looking for some advice as to how i could get round this and push this out via a TS. Is it at all possible to install the application as admin during an re-image TS? Regards Rufus  

The sccm deployment system is automatically deployed to partitions that already have systems.
  I have some computers with multiple hard disks. Suppose the environment has three hard disks in the computer. According to the sata1 sata2 sata3 arrangement, the system has the first partition system on the sata1 disk, and some of the first partitions on the sata2 disk. Some systems are in the system. First partition on sata3 disk
Then through the sccm deployment automatically determine the deployment to the sata1 disk or sata2 disk or sata3 on the first partition of the system, how to do it? The OSDDetectedWinDir variable does not seem to take effect. How do I set this task sequence parameter to the deployment system to automatically determine which disk partition the system is in, and install it in the corresponding partition.   sccm 部署系统自动部署到 已经有系统的分区上问题
 我有些电脑 多个硬盘，假设环境中电脑硬件 3个硬盘 按sata1 sata2 sata3  排列方式， 系统有的在sata1磁盘上第一个分区系统，有的在sata2磁盘上第一个分区，系统有的在sata3磁盘上第一个分区
那么要通过sccm部署  自动判断部署到sata1磁盘或sata2磁盘或sata3所在系统的第一分区上，改如何操作做呢？ OSDDetectedWinDir变量貌似不能生效，请问如何设置这个任务序列参数达到部署系统自动判断系统在哪个磁盘分区，就安装在对应的分区。

Hello, As per company policy I need to change passwords for SCCM service accounts: 1. network access 2. client push 3. domain join Microsoft suggests not to change password for network access account and consider to create completely new NA account. What's the best policy for client push and domain join accounts, based on some blogs online changing domain join account password still requires to re-build OS images, account is used in UDI wizard and task sequence step to join machines to domain. Any suggestions, particularly for client push and even more > domain join account password change policies, procedure for network access account can wait. Thanks, Vern