Re: [mssms] USMT MIG file Viewer

thanks.. resolved using "https://social.technet.microsoft.com/Forums/en-US/8316764b-2e20-4bb1-b78e-1deadb087739/how-to-manually-recover-user-state-data-saved-to-a-state-migration-point?forum=configmanagerosd On Mon, Jun 19, 2017 at 4:25 PM, Daniel Ratliff wrote: > I may be

RE: [mssms] RE: Auto reboots of servers during patching

H depends what a ‘Sound’ is…. Is it the pressure and displacement waves in the air… or is ‘Sound’ what we interpret what these waves as ?… Magnus Tveten From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Adam Juelich

[mssms] Replacing DMZ Distribution Point

Hello All, We are moving from a 2008 to 2012 server and have WSUS working on both at this point. The 2008 server is configured to deploy patches internally and externally. We have changed this so the 2012 server DP will only patch internet based clients. To replace the 2008 server with the

[mssms] SCUP Dell BIOS Updates

I've published metadata for a handful of Dell BIOS updates via SCUP. They've been in my console for a few weeks now and no clients show the updates as applicable: [cid:image001.png@01D2E8E6.26C9D7D0] I've never deployed anything from the Dell catalog in SCUP before but I assumed that clients

Re: [mssms] RegKeyToMOF error

when I save that, and run mofcomp -check testnew.mof, it tells me: C:\temp>mofcomp -check testnew.mof Microsoft (R) MOF Compiler Version 10.0.10586.117 Copyright (c) Microsoft Corp. 1997-2006. All rights reserved. Parsing MOF file: testnew.mof testnew.mof (28): error SYNTAX 0X80044002: Expected

RE: [mssms] RegKeyToMOF error

That was the bugger. Thanks! From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Sherry Kissinger Sent: Monday, June 19, 2017 8:16 AM To: mssms@lists.myitforum.com Subject: Re: [mssms] RegKeyToMOF error when I save that, and run mofcomp -check

[mssms] RE: RegKeyToMOF error

Bump From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray Sent: Thursday, June 15, 2017 4:44 PM To: mssms@lists.myitforum.com Subject: [mssms] RegKeyToMOF error Hi All, I'm trying to import my custom registry settings via a MOF file into

RE: [mssms] RegKeyToMOF error

From a cursory look, it appears the import is expecting a datatype “string”. If this is correct, line 28 should have quotes (either single or double depending on the syntax) around DellBIOSConfig3.2_Wed_LAN. The underscore is used as a new line character in some syntax. Ending lines without a

[mssms] RE: SCUP Dell BIOS Updates

If you have not yet, you need to add the Dell OpenManage Inventory Agent (for Dell Business Client Systems) to your systems for it to know if your machines need the Dell updates. It’s available, and regularly updated, through SCUP as well. Please note that it runs on reboot, so after it is

[mssms] USMT MIG file Viewer

Hi All, Looking for USMT.MIG file viewer. . USMT Showing as Successfull but user complaining files are missing from documents.. (SMP based USMT) I have USMT key and its encrypted farmate.. https://visser.io/2009/09/migrecover-for-microsofts-windows-easy-transfer/ Tried above But all show able

RE: [mssms] USMT MIG file Viewer

I may be incorrect, but the .MIG file is encrypted and only viewable by the source machine. I don’t know of any viewers, I always check scanstateprogress.log or loadstateprogress.log. Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of

[mssms] RE: SCUP Dell BIOS Updates

While we’re on the topic, how reliable do you guys find scup for updating the bios? I’ve considered it in the past but it seems high risk to me – eg. you could easily brick machines. For me, bios updates are one of those “if it ain’t broke don’t fix it “ type of things. From:

[mssms] Two mystery packages that can't be distributed after site restore

Last Sunday I did a site backup and restore to get our site server off Server 2008 R2 and onto Server 2016. It all went well, however, I have two mystery packages that have failed to distribute as listed in content status named: * Configuration Manager Client Upgrade Package *