dinci5

I have recently upgraded to SCCM 1606 and ADK 1607. My old custom boot image still works. It has not been updated by the upgrade process. I then created a new Boot Image based on ADK 1607. All went well. However, the F8 key doesn't trigger Command Prompt. Enable command prompt support is enabled in the Boot Image properties. I need this to work becuase my Task Sequence is failing and I have to troubleshoot. Anyweb?

I have the exact same problem. I've read something about the SMSTSSoftwareUpdateScanTimeout task sequence variable. Don't know yet how it works.

FYI.. On my test server I was not a sysadmin. The db_owner permission is not enough for the testdbupgrade. You need to be a sysadmin. problem solved

Already checked that site. It's not applicable for me. Thanks

Hi there, I need some help performing the testDBupgrade step before proceding with the actual upgrade. I followed this procedure: https://www.systemcenterdudes.com/sccm-installation-testdbupgrade/ Current environment is: SCCM 2012 R2 SP1 I'm using the 1606 baseline installation media. The SQL Server is the exact same version as the production server. CMD is started with elevated rights. SQL is not a named instance. (I first tried to do the test on a named instance, but that failed) I'm receiving below error: Attached you can find the complete log file. ConfigMgrSetup.log

If you don't need to run it on many devices, why not use PSExec.exe ? No need for SCCM. Also, if it is an uninstall of an already deployed application, why not deploy it to a collection as an Uninstall?

... Delete

For clarification... This is a Microsoft Surface Pro 3. We have already deployed 500+ of those successfuly and all other preloads are working just fine. That's why it's confusing why this devcie keeps failing. I have installed it successfuly with a clean Windows 10 ISO and joined to domain just to check if there might be something wrong with the device itself. Everything working fine. Then tried to preload again and it fails. SCCM is a great tool but it sucks when something is failing. It's so hard to figure out why.

I never managed to solve this problem. Now I have another device with this error. See smsts.log for details. In the SCCM Status Message Queries I see these errors: "The task sequence execution engine failed execution of a task sequence. The operating system reported error 617: You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used." And: "The task sequence execution engine failed executing the action (Error in the task sequence) in the group (Gather Logs and StateStore on Failure) with the error code 9803 Action output: . The operating system reported error 617: You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used." And: "The task sequence execution engine failed executing the action (Validate) in the group (New Computer) with the error code 9803 Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript.exe "C:\_SMSTaskSequence\WDPackage\Scripts\ZTIValidate.wsf"' SwdAction = '0001' Command line for extension .exe is "%1" %* Set command line: Run command line Working dir 'not set' Executing command line: Run command line Process completed with exit code 9803 Microsoft ® Windows Script Host Version 5.812 Copyright © Microsoft Corporation. All rights reserved. Microsoft Deployment Toolkit version: 6.2.5019.0 The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ERROR - Machine is not authorized for upgrading (OSInstall=N), aborting. FAILURE ( 9803 ): ERROR - Machine is not authorized for upgrading (OSInstall=N), aborting. Command line returned 9803. The operating system reported error 617: You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used." smsts.log

I was pretty sure, but as I made a mess of the server I started again from scratch. It works fine now. I'm pretty sure it's the same as before though. Thanks guys!

Okey, that is seriously one of the best things there is to troubleshoot TS errors. I will definitely try that one out. Thanks a lot Peter!

Hi, I'm testing WDS+MDT and want to deploy Windows 10 professional on a workstation. This works very well for now. The problem is that I receive the Product Key prompt after every installation. Is there anything that I'm missing? I have SkipProductKey=YES in CustomSettings.ini

I use this script, but slightly edited for my purposes: https://gallery.technet.microsoft.com/scriptcenter/Retrieve-OU-for-Computer-7a062402 So it's similar to what you posted. Perhaps it's because the script is ran with the SYSTEM account?

Hi, At the end of my OSD Task Sequence I run a Powershell script that generates a report and saves it in a certain location. Helpdesk uses this report to quickly check if all applications are correctly installed and a few other things. One of the things is a check for the OU of the device. When I run the script from within Windows it works just fine. However, during OS Deployment the OU cannot be read. FYI... The script does not rely on the ActiveDirectory modules. It uses the System.DirectoryServices namespace. Any ideas how to get it to work?

Could you be more specific? Nothing changed in the last year in our environment and everything is working just fine on all other sites. What exactly should I look for in the database and/or customsettings.ini I would rather leave customsettings.ini as is beacuse it works on all other sites.

Btw... The problem is only on one remote site. All other sites are working perfectly fine.

Hi, SCCM 2012 R2 SP1 We are unable to stage PC's on one of our remote sites with a local DP. The error we receive is just strange: 0x0000264B See screenshot... Also, attached you can find the smsts.log file. One of the things I notice in the log file is: FAILURE ( 9803 ): ERROR - Machine is not authorized for upgrading (OSInstall=N), aborting. Now I know I've seen this before but I really don't remember how I've solved it last time. The PC is in SCCM and the OSInstall variable is set to Y So not sure why it fails. It all worked well for over a year then it suddenly stopped working. Nothing has changed in our environment. Can anyone push me in the right direction? Thank you smsts.log

Thanks a lot. I'll go ahead plan the upgrade process So an upgrade directly to 1606 is not possible? I'll have to upgrade first to 1511?

Hi, We have deployed laptops with Windows 10 build 1511 for a couple of months now. What is the easiest way to upgrade these laptops to the anniversary update (build 1607)? We have SCCM 2012 R2 SP1 Thank you

What is your detection method for this script? If your detection method is just the detection of the presence of this shortcut: "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Skype for Business 2016.lnk" Then your script will never run as this shortcut already exists (but is incorrect) so it will detect the presence and consider it successful without running it. So, what is your detection method to check whether the script ran succesfully? You can, for instance, create a reg key at the end of the script and use that as a detection method. Otherwise you could create a shortcut with a slightly different name (e.g. without 2016) and detect the presence of that one.

Thanks a lot. This is exaclty what I need. I'll check your blog out for sure.

I'm from Europe, so I'll skip the presentation This query is actually good. Problem is it gives me multiple hostnames as it is a monthly report. So if a software is used every month, the results will show the most recent usage per month. I now have to figure out how to select only all devices with the most recent LastUsage date

Thank you for cleaning up my code. SSRS seems nice indeed, but I really have not that much experience with it not with SQL. As you could see, my code is very messy. I don't know how to duplicate the existing queries so I can edit them

Hi Garth, In the first report you have to choose a month and a year. So you have to export multiple reports and combine them manually. In both reports you only see the hostnames and no logged on users. The reports are very limited. We, for instance, need to check if a software is not used in the last 3 months and uninstall it from that computer so we can use that license for someone who will actually use the software. --- What I really want is to have an SQL query to read this data so I can refresh it in Excel using Power Query. I do this for many other reports. With a push of a button you have the latest stats. Now, I have created a WQL reporting query that gives me exactly what I need. The query is: select SMS_R_SYSTEM.Name, SMS_R_SYSTEM.LastLogonUserName, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.OperatingSystemNameandVersion, SMS_MonthlyUsageSummary.LastUsage from SMS_R_SYSTEM inner join SMS_MonthlyUsageSummary on SMS_R_SYSTEM.ResourceID = SMS_MonthlyUsageSummary.ResourceID inner join SMS_MeteredFiles ON SMS_MonthlyUsageSummary.FileID = SMS_MeteredFiles.MeteredFileID WHERE DateDiff(day, SMS_MonthlyUsageSummary.LastUsage, GetDate()) < 90 AND SMS_MeteredFiles.RuleID = 16777318 -> TIP: The RuleID is actually the Internal Rule ID (you have to show that culomn in the Assets and Compliance > Software Metering view) The only problem is that It displays some hostnames multiple times with different "Last Usage" time. --- Can I, somehow, get hold of the query that is executed when a Software Metering report is generated?

Hi there, I really, really dislike the Software Metering reports in ConfigMgr. I'm not that skilled in WQL/SQL to create custom queries myself. Does anybody have an idea how to create a custom query that will: List all devices where a metered software has run in the last 90 days List all devices where a metered software has NOT run in the last 90 days Include in report: Device Name, Username, mast run date Thank you