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,504 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 key. A lesson I won't forget!
  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 query. Apparently the download never happened but the update was deployed. When the clients tried to download the file, it didn't have anything to download!
  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 can attach it to this thread. No; removing the driver package does not remove the driver from Configuration Manager. When dealing with drivers, you have them in two locations. First, you have to import the driver into Configuration Manager. Think of this as getting it into the Configuration Manager application. This is exposed under the Drivers node. Once you've imported the drivers, you have to create a driver package. This is content, meaning it allows your clients to actually use the driver. This is exposed under the Driver Packages node. If you want to remove the driver completely from the Configuration Manager, you'll have to remove the driver and then update all of your distribution points with all the packages that contained that driver.
  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 seconds due to bandwidth control, the current sending rate is 10 percent, the estimated bandwidth is 480597 bytes per second SMS_PACKAGE_TRANSFER_MANAGER 12/11/2013 7:34:35 PM 6300 (0x189C) Yield 19 seconds due to bandwidth control, the current sending rate is 10 percent, the estimated bandwidth is 480597 bytes per second SMS_PACKAGE_TRANSFER_MANAGER 12/11/2013 7:34:35 PM 5508 (0x1584) Yield 45 seconds due to bandwidth control, the current sending rate is 10 percent, the estimated bandwidth is 200248 bytes per second SMS_PACKAGE_TRANSFER_MANAGER 12/11/2013 7:34:35 PM 6148 (0x1804) Yield 45 seconds due to bandwidth control, the current sending rate is 10 percent, the estimated bandwidth is 209715 bytes per second SMS_PACKAGE_TRANSFER_MANAGER 12/11/2013 7:34:36 PM 5780 (0x1694) Yield 18 seconds due to bandwidth control, the current sending rate is 10 percent, the estimated bandwidth is 524288 bytes per second SMS_PACKAGE_TRANSFER_MANAGER 12/11/2013 7:34:38 PM 6588 (0x19BC) Prior to the upgrade, I could actually a line between these that would tell me it was sending x bytes to the server. Because of my upgrade problems, I'm wondering if something is broken. Can someone check their logs and let me know if you see this missing line, or if it's just me? I appreciate your help! Thanks!
  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 interpit the logs as saying this: 5:12 - Install Office 5:18 - Are you done? (no response) 5:23 - Are you done? (no response) 5:28 - Are you done? (no response) 5:28 - This step failed, and the Task sequence says to not continue if this task fails, so abort
  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 insight is helpful and much appreciated. Thanks,
  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 Active Directory. For manual installs, you use Server Manager. But like I said, you won't need to do this. Once you have your 2012 machine up and running, just create a policy for it your Win8 machines and apply it only to those machines. Make sure you manage the Win8 policy with the 2012 machine and then continue to manage the older operating systems the way you did in the past.
  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 created specific collections that do nothing other than provide a maintenance window. This seems the easiest way to manage in my environment. Now, each maintenance window has it's own collection and I can add machines and easily see what the maintenance windows are with a few powershell commands. At present, I only have one maintenance window defined. I have gone through and removed them from all collections except one. However, using both PolicySpy and Client Tools I see multiple maintenance windows. I have updated the machine policy, but I still only see these multiple maintenance windows. Is there somewhere that I'm forgetting to look where a maintenance window can be configured? EDIT: Maybe I'm reading too much into this. I reviewed the built in report "Maintenance windows available to a specified client" and all looks well.
  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 MicorsoftPolicyPlatformSetup.msi authenticode signature, and I'm not quite sure what to do about it. Since the majority of my clients installed without problems, I'm pretty sure the problem isn't with the source files. To make sure something wasn't getting corrupt data copied over, I did a file compare (fc <file1> <file2>) from a command prompt. The files are identical. I thought maybe an error message might be getting hidden during the install, so I decided to run the microsoftPolicyPlatformSetup.msi manually and see what happened. No errors were generated. However, after installing this manually, I was able to push the client successfully from the console. Any ideas?
  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. Works like a champ. The hardest part is getting the variable attached to the computer object, but once you get past that, its cake. To manually add or view variables, look at the computer object in sccm in the collection node.
  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...