jbudd0649

Thanks, Is an SMSID the same as a Windows SID? I ran the following command against my domain controller: ntdsutil "sec acc man" "co to se dc1@mydomain" "check dup sid" q q The command created an empty log file. I assume that means ntdsutil couldn't find any duplicate SID's. My collection currently only has directly added members. When I first encountered the problem I was using a name query in the collection rule, but again, the collection only had 163 members and the software package was getting installed on PC's that were not showing as being members of the collection. If it was a problem with the query, I would have expected to see those PC's in my collection that were unintentional.

I did indeed. The application is called GoGuardian. I created a GoGuardian collection and deployed the package only to that collection. I had a query rule running based on PC name, the collection only had 163 clients. When I looked at the status messages for the deployment I saw clients that were not in the collection. I deleted the automatic query rule and manually added clients to the collection. I then re-created the deployment, again only targeting the GoGuardian collection. When I came in this morning and checked the status messages, I no longer see random clients installing the software. I don't understand why PC's outside of the collection would have gotten the software, maybe there was a problem with my query rule, but that doesn't explain why the random PC's got the software but didnt show as being part of the collection.

I have a new software package that is only supposed to be installed on PC's in a specific collection. I configured the collection to query based on PC name. I have 163 members in the targeted collection, and for some reason the app is appearing on PC's that do not appear in the collection. I can see that the software package is only being deployed to the one collection. I have never seen this behavior before. Any ideas?

I fixed the issue. I'll leave my solution here for anyone that might have the same issue in the future. I ended up running my Windows 11 build and capture task sequence over again but this time I added a step after the Setup Windows and Configuration Manager to set the power plan to High performance in my base image. Then I used the new base image with the High Performance power plan in an OSD task sequence. The PC stayed awake through the whole TS so I just added a step at the very end of the TS to set the power plan back to balanced. I use SCCM to control the Power settings of all devices so I am not sure if it was necessary to manually set the PC back to balanced, but at any rate my issue is solved. Thanks

I have a OSD Task Sequence for Windows 11 22H2 being deployed to new Dell Optiplex 7000's. The Dell's are going to sleep during the "Setup Windows and Configuration Manager" step of the Task sequence. I have checked the "Run as high performance power plan" box in the more options tab, but the PC still goes to sleep. I have also tried using a run command to set the power plan to high performance "PowerCfg.exe /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c". The run command works fine in Windows PE, but doesn't persist when the task sequence boots into Windows to start the setup phase. I tried adding the run command right before the setup phase and right after the setup phase. No matter where I put the run command it doesn't seem to matter. If I don't touch the mouse or keyboard before the PC goes to sleep the TS halts. Once I shake the mouse it will continue where it left off. If I put the run command just above the "Setup Windows and Configuration Manager" It runs fine and if I hit F8 and run "powercfg /getactivescheme" it shows that the system is in high performance mode, but then when the system reboots into the installed OS the powerscheme has reset to balanced. If I put the run command after the "Setup Windows and Configuration Manager" step, then the pc goes to sleep because it runs after the fact. I guess I am asking how to set the powerscheme to high performance once the PC has booted into the installed OS but before the "Setup Windows and Configuration Manager" portion starts to run. I saw some posts from years ago on Reddit talking about connected standby and using a registry setting to change it to disabled, however I still don't know where to put the reg tweak in my TS and it seems like the adition of the "Run as high performance power plan" option was supposed to fix this. Thanks

I am using the WOL Proxy in our environment. When the machines are completely powered off the WOL proxy service wakes them with no problem and they run updates and TS's with no problem. However, if they are in sleep mode the WOL proxy service is not able to wake them. I have updated the BIOS on my PC's and enabled WOL and disabled the advanced sleep states like S4. I cannot figure out why the machines will wake when completely powered off but wont wake from Sleep. We are running Windows 7 enterprise 32x. Thanks

In our environment I have 1 primary site server running the SUP role and 5 DP’s, 1 at each of the buildings connected to our WAN. Originally I was installing updates during business hours. I made sure all of my deployments had the Suppress reboots on Servers and Workstations option selected. I also chose to hide all notifications. I expected that the SCCM clients would install updates and keep on kicking like normal without the user having any idea what is happening. Instead I saw that the updates were being installed but the users were being forced to reboot the PC’s. This is a problem for obvious reasons. I tried to extend the grace period for the reboot in the device settings to 8 hours with a 20 minute timer that couldn’t be closed. This didn’t help any, users still complain about reboots during the day and they HATE the dialogue that can’t be closed. In order to remedy this, I configured a maintenance window from 1:00 AM-4:00 AM. I enabled the send wake up packets on all deployments and also enabled the wake up proxy in the client settings. I tested to make sure that clients would indeed wake to run the deployment. I no longer have users complaining about reboots, however when I look at the compliance on the deployments, they are showing TERRIBLE compliance. Out of 2176 machines only 247 are compliant. I can’t figure out why. My best guess is that during the maintenance window my PC’s are either not waking, or they are out of the building (We have a lot of laptops). Or they are not rebooting for some reason. I would like to go back to installing updates during the day because I know all machines will be in the building and powered on, but I don’t want to make the users unhappy with mandatory reboots. Is there a way to configure the SCCM client to allow the users more control over the reboots? I would like the client to notify the user that a restart is required, but I don’t want it to force the reboot. I have seen screen caps online of a dialogue that allows the user to “snooze” the restart for a given amount of time, but have never seen it myself or figured out how to turn it on. I have attached images from google to this post. Thanks for any reply's or help.

I'm still having issues with this. I have triple checked all of my packages and deployments. I have scheduled them all to install at 1:00 Am. I made my maintenance windows 12:00-3:00 AM. I configured a scheduled task to run at 3:00 AM to shutdown the PC's. When I look at the event logs I see the PC's powering on at 12:00 Am, I see the auto shutdown task at 3:00, and then at 3:01 the PC's start right back up. Some times I see them start at 5:00 AM for no reason. Any ideas? Thanks

I think I figured it out. I had an update deploying at 3:00 AM. I'm assuming that the PC's are waking for the update at 3:00 AM, since 3:00 is outside the maintenance window they aren't doing anything but sitting there.

I'm having issues with our Maintenance windows. I have configured my collections with a recurring maintenance window. The window lasts from 1:00 AM to 3:00 AM. All of my deployments are configured to send wake up packets. I have an automated shutdown task that runs every night at 8:00 PM. When I come in in the morning the PC's are all powered up because we have disabled all the sleep settings. The problem is when I look at the event logs I see the PC's are starting up at 3:01 AM everyday. I can't figure out why the PC's are ignoring the maintenance window, and instead starting exactly 1 minute after. Any ideas?

Thanks. Ill give that a try.

I have enabled Wake Proxy in my environment, I am trying to figure out a way to manually trigger a wake up signal without using a deployment. I downloaded the now micro right click tools and there is an option to WOL, however when I use this tool it only wakes PC's that are on my local subnet. Is there a way to manually trigger a system to wake up using the WOL proxy function?

After Deploying a PC using OSD, the SCCM Client isn't registering. I am able to see it in the console, however, I am not able to remote control it. Also when I look at the client actions from the control panel I only see "Machine Policy Retrieval & Evaluation Cycle" and "User Policy Retrieval & Evaluation Cycle". I have a single primary site SCCM 2012 R2 running on Server 2012 R2. I have 3 Servers running Server 2008 R2 with the MP and DP roles assigned to them. All communications are done via HTTP. The domain firewall is turned off on the site servers and on the client workstations. I have tried re-installing the MP role on all Servers. I see the 87D00231 error in the ClientIDManagerStartup.log, and I see "Failed to send management point list location Request" errors in the LocationServices.log. I believe all of my boundary groups are configured correctly, I have quite a few of them. The clients eventually do connect to the management point if I leave them to sit overnight. I haven't been able to figure out what is causing this behavior.

I too am having this issue, however i see "error 87d00231" in the logs. I am not using HTTPS in my environment. The other strange thing I'm noticing is if I let the workstation sit overnight, in the morning everything is as it should be and the logs show success connecting to the MP. I have one SCCM 2012 R2 primary site running on Server 2012 R2, and several MP's and DP's running on Server 2008 R2 in my environment. I'm wondering if that has anything to do with it. Do you have multiple site servers with these roles installed?

I was wondering if there was a general rule of thumb as to when to use this step in a task sequence. I have around 20 applications to deploy in one task sequence, I figure it is probably a good idea to throw a restart or two in there. Any thoughts on this? Thanks

Thank You. That was exactly what I was looking for.

I am trying to figure out which logs I should be looking at to verify which distribution point my client is downloading and installing packages from. I have two DP's each has their own boundary. I am trying to confirm that the clients in the respective boundaries are getting the packages from the right server. Thanks

I am getting errors trying to apply updates to my wim images using the scheduled updates module. The updates are failing to be applied, I am seeing errors 2096, and -2146498512 in my offline servicing mgr log. I have sccm 2012 SP1 installed. I added D:\ConfigMgr_OfflineImageServicing\*.* to my SCEP realtime scan exception list. I have also made sure that the sccm servers computer account is in the local administrators group. I tried uninstalling and re-installing the adk. The target wim file is windows 7 SP1. Here is my log and a sample. Checking if update (1 of 47) with ID 16806671 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:07:49 PM 7972 (0x1F24) Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\c45768b6-a646-467a-b78d-7a555da92fc5\windows6.1-kb2647753-v4-x86.cab. SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:08:01 PM 7972 (0x1F24) Applying update with ID 16806671 on image at index 2. SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:08:01 PM 7972 (0x1F24) Failed to install update with error code -2146498512 SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:08:07 PM 7972 (0x1F24) InstallUpdate returned code 0x800f0830 SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:08:07 PM 7972 (0x1F24) STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCM2012.wcps.k12.va.us SITE=CMS PID=2572 TID=7972 GMTDATE=Mon Jun 17 19:08:07.854 2013 ISTR0="16806671" ISTR1="CMS00041" ISTR2="2" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:08:07 PM 7972 (0x1F24) Failed to install update with ID 16806671 on the image. ErrorCode = 2096 SMS_OFFLINE_SERVICING_MANAGER 6/17/2013 3:08:07 PM 7972 (0x1F24) offline service mgr.log

' Hide the progress dialog Set oTSProgressUI = CreateObject("Microsoft.SMS.TSProgressUI") oTSProgressUI.CloseProgressDialog Set oTSProgressUI = Nothing I found this script that will hide the task sequence progress bar, the problem is I have no idea how or where to put it in my task sequence. Could someone throw me a bone please?

I am looking for a way to limit the amount of task sequences I see when I PXE boot a machine to start the imaging process. I share a SCCM 2012 server with 5 other technicians, we advertise all of our task sequences to the unknown computers collection so that we can do bare metal imaging. Right now when I PXE boot a PC I can see around 30 task sequences. I want to see only the task sequences I use, and my co-workers to only see the task sequences they use. I assume this can be done somehow through scripting, but I am a complete noob in that department. Any help is appreciated.

Looks like I was confusiong two different problems as one. I had to add the windows 7 install.wim to the operating system images I was then able to select it in the task sequence. Im still not sure about the errors in my log file though...

Im having a pretty strange issue that I haven't found an answer to yet. Everything was working smoothly until I got to this portion of the guide. When I try to create the task sequence in SCCM I cannot see the distribution point. I can see and select the boot image, but when I try to select the operating system install package no distribution points are listed. The OS install package was distributed to the distribution point in a previous portion of this guide. When I look at the properties of the OS install package it shows the DP. I tried uninstalling WDS and now I see a boatload of errors in my distmgr.log file SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:51 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) Processing CMS00005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) Removing CMS00005 from D:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) Removing D:\RemoteInstall\SMSTempBootFiles\CMS00005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RegQueryValueExW failed for Software\Microsoft\SMS\DP, INST_WDSAUTO SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) WDS is INSTALLED SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) CcmUnregisterWDS SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) Removing SMSPXE provider. Performing an uninstall SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) PxeProviderUnRegister SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) PxeLoadWdsPxe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) wdspxe.dll is loaded SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770) WDSServer status is 4 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) WDSServer is STARTED SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) Removing existing PXE related directories SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) Removing PXE Boot directory: D:\RemoteInstall\SMSBoot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) Removing PXE Temp directory: D:\RemoteInstall\SMSTemp SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) Removing PXE Images directory: D:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) Removing PXE Images directory: D:\RemoteInstall\SMSTempBootFiles SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770) SetFileAttributesW failed for D:\RemoteInstall\ Here are some jpg's. https://www.dropbox.com/sh/ff1gn37tzjiiff8/515ddou8yx

We are running SCCM 2007. I am running out of space on my server and do not have the resources to add more space at this time. I have all my images saved to E:\images$. My distribution point is on the same server also in E:\. Is it possible to delete the original image source since the image is duplicated into the distribution point. It seems silly to have a 15 gig image sitting on the server in two different locations taking double the space needed. Any suggestions?

When I run Windows update on the clients I'm getting the no updates required message. I have searched my entire C and D drive but cannot find wuahandler.log. Any ideas??

Does anyone know if it is possible to remote control a PC based on the currently logged on user ?? We recently switched from a Novell based network to a Microsoft based network. In the old environment all windows machines were managed using the Zenworks client for Microsoft and cosoleone. I could open consoleone search the tree for a user and click remote control. This allowed us to remote control the selected user no matter what workstation they were logged into. Now in order to remote control with SCCM 2012 I have to know the machine name of the logged on users PC. Getting the user to find and tell me the name is sometimes a nightmare. Am I missing something, or is this functionality not part of SCCM? I really loved having that functionality and it's going to be such a bummer if we can no longer do this. Thanks