Residualfail's questions

I'm configuring GPO's for Windows Storage Sense. The GPO's are very straight-forward and Storage Sense itself is a simple concept. One thing that bothers me though, what exactly does Storage Sense classify as "Temporary files"?

I'm attempting to do some basic testing against storage sense to make sure it's working as expected and I can't get it to clean my C:\Windows\Temp or C:\Users<username>\AppData\Local\Temp and Downloads directories. I'm filling up my drive with junk to trigger a low disk space event, even changing timestamps to back date them to make them look older but storage sense just won't touch them. I have several GB's worth of data scattered in directories that should be getting nuked and they're left untouched.

I'm sure it's trying to be smarter than just blowing everything older than 30 days up and I'm fine with that. I'd just like to know what the rules are so I can explain it.

Is there a technical breakdown of what exactly (directory\file basis) is evaluated and removed by storage sense?

We have an MBAM server and tested policies which work normally for nearly every machine we've migrated. Though, I have seen 3 systems now that prompt for a recovery key instead of the users PIN. After recovering, each subsequent reboot asks for recovery keys again, requiring end users to contact support after each reboot. The recovery keys are being escrowed into AD\MBAM just fine.

Seeing as the process has worked on roughly 99% of systems so far, I'm assuming we're dealing with hardware or software level issues. In one case, I have reloaded the system and had BitLocker begin working normally indicating it was some machine state issue.

I've been through the gambit in terms of troubleshooting the TPM state, firmware upgrades, reviewing BitLocker logs, fully decrypting\re-encrypting devices but once the laptop is in this state, it always prompts for recovery.

Is there a way to discover which PCR exactly is triggering the recovery state so I can focus on a single PCR? We're about to go company wide with this process and I'm concerned that we might disrupt more users during migration. I'd at least like to have a plan to troubleshoot.

I am using USMT 10 and have successfully migrated a user profile. However, the new profile resets the default file associations for most applications back to the Windows 10 defaults (Edge, Photos, etc). For example, by default we use Adobe Reader for PDF's, but on sign in pdf's are reset to Edge as the default viewer.

We have established a default file association xml as part of our OSD which is working just fine. It's only profiles that are migrated with USMT that are breaking. New profiles on the system are working as intended.

Is there any way to exclude the users file associations during migration?

My company is using SCCM. I have run access to one of the default reports called "Monitoring\Overview\Reporting\Reports\Network\MAC - Computers for a specific MAC address".

It returns all computer names attached to a specified MAC. I'd like to run this report from PowerShell and dump the computer names either straight to console or a text file.

I'm having a hard time figuring out what cmdlet I'd use to do this. Is this possible?

I'm trying to capture a WIM of my reference machine. I setup a Sysprep and Capture task in MDT, ran it and used the default UNC path which is in the captures directory of my deployment share. The task will execute and initiate the LTI capture process. The system restarts, boots into LTI, and begins capturing but the process hangs at the "Running action: Create WIM" step. It usually hangs at 2.0% but I've seen it reach anywhere between 1-6%.

When I check the captures directory, a .wim file was created, but it's <100MB. I've let the process run over night with no additional progress so it's definitely just hanging.

My reference machine is a hyper-v VM hosted on a dedicated machine for building images, but separate from my MDT server.

Which logs can help me figure out why it would be hanging?

And as another option, is there any way I can change the UNC path to point to a local HDD on my hyper-v server that I can manually copy up to MDT later? When I tried redirecting it to a local share on my hyper-v server, it said the UNC path couldn't be connected to.

I have an ESXi virtual machine running Windows Server 2012 and WDS. The server VM has a secondary hard disk which is storing my boot and install image files.

When I try to capture an image, it wants me to save it to a local drive on the reference machine but for practicality's sake, I'd like to avoid having to truck a USB drive to each system I need to capture. There will be a few...

Is there a way I can capture directly to my servers secondary HDD? How else can I get the image to my server without physical presence or interaction on the remote machine?

I've been tasked with finding a way to generate a report to document new desktop\laptop computers that are both joined and removed from Active Directory (Server 2008).

Is there a way to pull a report directly from AD for all systems joined\removed in the last 30 days? My other alternative is to manually record systems as calls come in and get closed but that could be prone to error and time intensive.

Disclaimer: I'm not very familiar with reporting features in AD and have limited permissions to control computer objects in AD (add, modify, remove), though once I find the process I'll be giving it to someone else for implementing.

We're just switching our images over from good old ghost .GHO's to .WIM format. One of the reasons is that we have heard that software updates could be modified/installed in .WIM's offline.

For example, right now if we wanted to move from Adobe Reader X to Adobe Reader XI, we would need to drop our base, uninstall Reader X, install Reader XI, reseal our sysprep'd image, then recapture in Ghost.

Unfortunately the only process I can find looks like it only applies to Windows Updates. Other walkthroughs I've found show how to deploy the software as part of a task sequence in SCCM which I don't have access to and our customer does not actually have the network infrastructure to support.

Is this possible or did we misunderstand the scope of the offline updating feature?