rem7777

Hi, has anyone found an equivalent tool for the Surface Pro 4? I'm at a loss as to how to set the UEFI password during OSD for SP4s.

I've checked a few of the machines reporting client version 5.00.7958.1000. The control panel applet also shows this as the version, so I'm inclined to think that the report is accurate. Any idea how I can troubleshoot the automatic upgrade process?

Thanks Peter - The SCCM primary was upgraded in May last year

Thanks Jaybone - That's interesting! I've taken my figures from the “Count of Configuration Manager clients by client versions” report - I'll do some checking tomorrow to find out whether they're actually the version showing on the report.

I recently inherited an SCCM 2012 R2 environment from a colleague. The primary was upgraded to 5.00.7958.1604 in May 2015 (just before the release of R2 SP1). 'Automatic Client Upgrade' is enabled, but only 60% of the clients seem to be on the correct version: 5.00.7958.1000 = 40% of computers 5.00.7958.1604 = 60% of computers Is there any troubleshooting I can do to find out why these clients haven't upgraded? As I understand it, the clients should've detected that a new version of the client was available and scheduled an upgrade during the period defined in the 'Automatic Client Upgrade' settings (in this case 7 days). Appreciate any advice on this.

Hi, I'm having a problem running a task sequence from stand-alone media. I get the following in smsts.log: Expected hash for app/content: Content_720926a3-e8d0-439a-ba43-ee76b95aa63d, 32780, A8671204BF3878B70B6C1060F6756E8C7BC5353F0660AB9D4A46DF5AE3E8D9C8 V4HashCompatibilityMode: FALSE Computed hash: A4C0688F85BD5E908D212FD9727767E3930D81B9BBC849B7A4475D490D4941AE Failed to run the action: Install Application. The hash value is not correct. (Error: 80091007; Source: Windows) I can run the same task sequence from the network and it completes successfully. I've tried refreshing \ removing \ resending the content to the DP I used to create TS stand-alone media and I've tried removing the application from the task sequence and re-adding (and recreating the stand-alone media after each change) I'm currently creating another copy of the application, pushing this source around and adding this to the task sequence but even if this works, it is a workaround rather than a solution. Any ideas where else I can look to investigate this hash mismatch? I really don't understand why it deploys successfully during a network build but not from the USB stand-alone media