Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

SanjuNana's Achievements


Newbie (1/14)



  1. I need to clean up some old/outdated content and had a few questions on best practices. Right now I'm working on Software Updates and their Deployment Packages. Our normal monthly procedure creates a Software Update Group with required updates, as well as a Deployment Package. So for 2015, we have 12 Software Update Groups and 12 associated Deployment Packages. I'm currently rolling all of the 2015 updates into one Group and one Deployment Package, and need to remove not only all of the Deployment Packages, but I want to make sure that it also removes the content from the associated Distribution Points. What's the best practice way to do this? If I just delete the deployment packages from the console, will it remove the content? (I doubt it, since you can go into the Properties of the deployment packages and remove the content from the 'Content Locations' tab. But of course you can only remove them one at a time in the GUI and that would take WAY too long for 12 Deployment Packages that are on 13 distribution points.) the Remove-CMContentDistribution or Remove-CMSoftwareUpdateDeploymentPackage cmdlets seem promising, but we don't have a test environment, and I'm not yet a Powershell guru, so I want to make sure that I know what I'm doing before just trying them out in prod. Can anyone provide me with some -Examples of their proper usage (or a better powershell way to clean up outdated content from DPs)?
  2. Thanks for the suggestion. I verified that the time was the same on box the Primary site and remote distribution point. Tried removing the distribution point role and re-adding it while it was on location, but same result. Can't connect; access denied. The access denied message continues to confound me, since it would have had to have had access in order to install it in the first place, and nothing changed between the time that it was built in lab and when it was brought up at the remote site (other than the IP address of the remote box, of course).
  3. This is my first Windows 8.1 distribution point build (our other remote servers are Windows Server 2012 secondary site/management points). It was built successfully in my lab, Distribution Point Configuration Status in Monitoring was all green and all content sucessfully finished distributing before we shipped the machine to its remote site. Once on site, it has never worked. I'm seeing either failed to connect to the distribution point or access permission issues in the Distribution Pojnt Configuration Status details (but the CAS And Primary computer accounts are in the local Administrators group on thie DP). I can connect to \\computer\admin$\ In Administration > Distribution Points, however, when I select this DP and click on the 'Drives' tab -- there are no drives listed (although when I remote into the machine, I can see that the drive is present and the content is there (save for the newest content, which can't be distributed).
  4. Was out of town for training last week, but the issue is still happening. I'm convinced that it's a .NET Framework error somewhere, but have no idea what's causing it or how to fix it. To recap, I have a Windows 8.1 deployment that works prefectly for most of the hardware in the company - Dell Optiplex 980s & 990s, and Latitude E6420s & E6410s, but when the new hardware is imaged (Latitude E7420s and E7440s), it appears to work, but if you try to open an application that uses .NET Framework (SCClient.exe or Powershell ISE are the easist to see) those applications crash. This happens regardless of whether I install .NET Framework 3.5 on the machines. I have removed and added back each version of .NET Framework, and the applications still crash. I've tried the .NET Framework Repair tool (version 2), and it did not resolve it. The error is always the above. (Unhandled exception code c0000005)
  5. More error logs: Application: SCClient.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00000000 Also, interestingly this is only happening on new hardware (we recently got 2 new models of laptop - Dell E7440 and Dell E7240) ... note that both were imaged a week prior with the same image, drivers, task sequence, etc. and were working perfectly. I just imaged a desktop (Dell Optiplex 990) and software center does not crash. I don't have an older model laptop to test with at the moment.
  6. Tried both ways - with 'Install all updates' as task sequence and with it disabled. Once imaged, though, updates will also be sent to the machines (as I've had inconsistent results installing updates during OS imaging). I checked Silverlight version and it was a bit off; installed update to latest version - same error.
  7. 8.1 media; I actually removed the .NET framework install from the task sequence and Software Center is still crashing. [installing with the following: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"\\[PATH-TO-WINDOWS-8.1-MEDIA]\sources\sxs" ] So, I've tried the following: Installed .NET during install with above. Crash. Installed .NET after install (both via above and via download from Internet). Crash (both before and after installing .NET) I'm now starting over from scratch -- I've disabled everything in the OS task sequence other than installing the OS and ConfigManager client. Same issue. Software Center crashes immediately. No .NET 3.5 installed, but I'm sure now that once installed afterward, it'll still crash. Uninstall/reinstall of SCCM client is also not resolving it (whether push install or manual install from CAS or MP).
  8. Hello all, I had been working on Windows 8.1 deployment and was going great until I had to take some unexpected time off from work. When I got back, it looked initially like things were progressing along and we were about ready to deploy the new PCs with Windows 8.1, but I noticed that Software Center was crashing. SCClient has stopped working. Error details below Problem signature: Problem Event Name: BEX Application Name: SCClient.exe Application Version: 5.0.7958.1000 Application Timestamp: 5230d2b7 Fault Module Name: StackHash_5861 Fault Module Version: Fault Module Timestamp: 00000000 Exception Offset: PCH_E1_FROM_ntdll+0x0003C1AC Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.3.9600. Locale ID: 1033 Additional Information 1: 5861 Additional Information 2: 5861822e1919d7c014bbb064c64908b2 Additional Information 3: 01d7 Additional Information 4: 01d7340064827245f2249cd1f1a7c264 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=280262 If the online privacy statement is not available, please read our privacy statement offline: C:\WINDOWS\system32\en-US\erofflps.txt Initially thought that it was a problem with the .NET framework 3.5, but I've uninstalled/reinstalled multiple times & nothing. Uninstalled and reinstalled ccmclient from Primary site several times. Nothing. Note that ccmclient/Software Center are still working on Windows 7 image. We're at SCCM R2 on all sites, (7958 client version). (SCNotification will also crash when restarts are pending, if you try to open the restart window. Looks like client is still functioning ok.)
  9. In our old SCCM 2007 system, we had created a number of AD Secirity Groups for software installations, then a ton of SCCM collections that would query the devices for that security group. We'd then target advertisements to those collections for software deployment. In 2012, I'd like to use the Requirements tab to query for that Security Group, but I'm having some trouble with it. I can query for the OU, but not the actual security group.
  • Create New...