Jump to content


Joe

Established Members
  • Content Count

    33
  • Joined

  • Last visited

  • Days Won

    1

Joe last won the day on August 15 2014

Joe had the most liked content!

Community Reputation

2 Neutral

About Joe

  • Rank
    Advanced Member
  • Birthday 05/19/1976

Profile Information

  • Gender
    Male

Recent Profile Visitors

3,706 profile views
  1. Sure. When dealing with configuration baselines and registry settings -- When you are creating an Execution Policy that looks at registry keys in HKLM\Software, make sure you tick the box for "This registry value is associated with a 64-bit application" if you don't want the rule to look in HKLM\Software\wow6432node. I was setting a windows setting, which wasn't really associated with a 32bit or 64bit "application". I passed by this setting without really thinking about it. I ended up creating a really weird text string that I could search for and found it under the wow6432node
  2. Nevermind; it really was a stupid mistake that cost me half a day.
  3. Sorry to bump an old post, but I wanted to share my solution to this same issue. While the solutions above didn't resolve my problem, it sure helped me find it! I recently had a handful of users report that a single software update was stuck deploying. It was hanging at the 0% downloaded phase. I couldn't really find any errors, but that may just be me looking in the wrong log. Anyway -- back in the sccm console, I did a quick search for software updates. I looked for everything that was deployed but not downloaded, and guess what I found -- this update was the only one that met my
  4. Thanks for this note. I was having this problem and just implemented it. I'll know in 20 minutes if it worked! EDIT: Fixed my issue! Thanks again!!
  5. He's asking you to put the drivers back into your build, and then run through another test deployment. When the machine fails, there is a file called smsts.log that will tell you why. It should be on the client you're building. I usually get this file for debugging by enabling debug support (F8) on the boot image. As soon as it starts to deploy, I press the F8. This opens a command prompt. Move this out of the way so you can see the failure. The command prompt will stop the machine from rebooting. Once you get the failure, then copy the file off the machine to a place where you c
  6. Greetings: I recently upgraded to R2. I had a problem with the database halfway through the install. According to the install, it completed successfully, but I've noticed that I'm not seeing some entries that used to be in pkgxfermgr.log. Prior to my R2 upgrade, I could actually see logs that would tell me what servers were receiving what packages. Now I only see logs like this: Sending thread starting for Job: 10752, package: CCM00089, Version: 1, Priority: 2, server: MYDP.Contoso.com DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER 12/11/2013 7:34:33 PM 6340 (0x18C4) Yield 19 secon
  7. It's failing to install Office 2010. It looks like the task starts to install Office 2010 Standard at 5:12, and then fails around 5:28. If you're deploying apps using a variable, make sure the app is configured to allow it to be installed without being advertised. Without that enabled, it will fail. 14 minutes is also interesting -- have you configured the install to run for only 14/15 minutes? If so, are you certain this is enough time to finish in your environment? Make sure the setup is 100% automated -- if it's not, it will never finish and you'll end up with this error. I
  8. Good Morning: I have a simple SCCM 2012 Hierarchy; a single Primary Site and many distribution points in the field. The Primary Site server is running out of disk space because of Software Updates. I need to replace it with a machine that has more disk space, as it is not currently possible for me to upgrade the disk on the Primary Site at this time. Does anyone have any recommendations on doing this, or possibly some links to documentation? I am considering a P2V of the primary site server, which should get the job done. But I want to make sure it's the correct path. Any in
  9. Wow; I really didn't read what you said. I'm sorry about that!
  10. You don't need to raise the domain or forest level to manage the devices. You only need to do this if you want to take advantage of the changes that Server 2012 introduced to Active Directory. Group Policies are technically not part of Active Directory, so they don't require the domain/forest levels to be at a specific version to work. You're definitely going to need to stand up a 2012 server. You can make it a DC if you'd like, but you don't have to. It just needs to be a member server in your domain. On a side note, DCPromo is still there and is only used for silent installs of Acti
  11. Greetings: I'm running into some problems with my maintenance windows, and I'm hoping someone can point out what I'm overlooking. I've been trying to find a way to manage maintenance windows in my environment. Initially I was assigning maintenance windows to the collections that provided the software updates (ie, a collection for Windows Updates with a maintenance window, a collection for Office updates with a maintenance window, etc). I've decided that this is rather confusing and is going to be difficult to tell when a machine has a maintenance window. To resolve this, I cre
  12. I am using SP1. Since it's a known issue and Microsoft is working on a fix, I guess I can just manually install on these machines to get the client going. It's odd, though -- shouldn't the expiration prevent (or at least generate a warning) the installation of the MSI manually?
  13. Greetings: I'm rolling out a new SCCM 2012 environment. I have 81 clients that I'm trying to bring into my environment from an existing 2007 environment. I configured discovery so they were identified by configuration manager, and then pushed the client to all of them. About 20% of the machines are failing to install the client, and they're all getting the same error: c:\windows\ccmsetup\logs\ccmsetup.log: Couldn't verify 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101 It appears that the installation isn't liking the Micors
  14. I use a front end to allow the person building the machine to totally customize the build. Each option is represented by a variable that gets attached to the computer object in sccm. If you look at the second tab on all task sequence steps, you'll see a spot where you can tell the step to only happen if a task sequence variable is set to a specific variable. When you run the sequence, if there is a variable on the computer object, it "becomes" a task sequence variable and you can use it to control what happens. I use about 40 different variables to control my Windows 2008 builds. Work
  15. Have you tried disabling 64bit redirection on the task? I'm not sure if that is causing your problem, but I always tick that box when I'm trying to make a systemwide change... just to make sure something isn't redirected since ccm is a 32bit process.
×
×
  • Create New...