Jump to content


Trevor Sullivan

Established Members
  • Content Count

    130
  • Joined

  • Last visited

  • Days Won

    8

Trevor Sullivan last won the day on June 13 2015

Trevor Sullivan had the most liked content!

Community Reputation

19 Good

About Trevor Sullivan

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://trevorsullivan.net

Profile Information

  • Gender
    Male
  • Location
    Chicago, IL
  1. You'd have to compare and contrast the list of updates you're deploying in Configuration Manager with the list of updates that is being shown in the Windows Update screen. See if there are any major products (eg. Microsoft Office 2013) missing from your SUP configuration in Configuration Manager, that have updates shown in the Windows Update screen. Cheers, Trevor Sullivan
  2. Hello Scott, Trusts There should be a two-way transitive trust between the parent (forest root) and child Active Directory domains by default. Schema Extensions There is only one schema for an entire Active Directory forest. Someone who is a member of the Schema Admins security group for the forest will need to apply the schema extensions. All they have to do is execute the extadsch.exe file off of the Configuration Manager setup media. Keep in mind that the schema updates are not mandatory for using Configuration Manager. It merely simplifies client service location requests. [Microsoft Technet] Planning for Service Location by Clients Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  3. Saying that the Application model isn't designed to be used in a Task Sequence would not be accurate. Is it buggy? Sure. Did Microsoft think through everything before they implemented it? No. But, that doesn't mean that it wasn't designed for use in a Task Sequence either. The very existence of the Install Application task sequence item type proves that it was intended for this purpose. One thing that Microsoft left out was the ability to declare a PowerShell execution policy that applies during the Task Sequence. If you don't put in a couple of registry hacks within your Task Sequence, then PowerShell script-based Detection Method rules for your Application Deployment Types will fail. For what it's worth, I've probably spent a total of 40+ hours (honestly, that is a conservative estimate) working on this issue, and have not come up with any firm answers. In my most recent testing from today, I have discovered that by reverting to an older Build & Capture Windows 7 Enterprise 64-bit operating system image (WIM), the Install Application task sequence items in the Deployment task sequence seems to be working successfully. The best I can guess is that there is something inside the newer Build & Capture WIM that is breaking the Install Application task sequence item. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  4. What do you mean by "scan disk?" ConfigMgr doesn't automatically run any type of disk scanning jobs. If you're talking about hardware or software inventory, then you would control those features by using the Client Settings package node in the ConfigMgr console. You would have to create a custom Client Settings package, and then deploy it to a collection of systems that you want to target. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  5. Jon, As long as you make all the appropriate modifications to the advertisement, you should be just fine. On the "new" computers, the advertisement would not run until the new schedule is met. If you remove the old, mandatory schedules, the "new" computers will not see them. That being said, I would suggest that it's probably not good practice to re-use advertisements. And as always, test this functionality prior to putting it into production. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  6. Hello, If you are having problems installing the ConfigMgr client, then I would imagine that you should be looking at ccmsetup.log? What errors are you getting in there? What is the target operating system you're working with? Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  7. Hello, You can still call batch files (.cmd or .bat extension) in System Center 2012 Configuration Manager. It sounds to me like your clients are getting a corrupted policy pulled from the management point. Are you sure that your infrastructure is healthy? Are you using the new application model, or regular package/programs? Have you examined the site server logs to see what's going on? What operating system is your primary site(s) running on? Have you applied Cumulative Update 1 (CU1) to your ConfigMgr 2012 site(s) and client agents? Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  8. Posting contents of an e-mail exchange: Although you may have enabled command support (F8) testing in your boot image, you must update the boot image on your distribution points for this change to take effect. Since you are not using PXE booting, you must also manually update your boot media after the distribution points have finished updating. The 0x80004005 (Access Denied) error message that you are receiving can be caused by many different reasons, not necessarily permissions related. For example, you might receive this if there is no network connectivity to the ConfigMgr site server, which is obviously not a permissions-related problem. This can happen if: The client cannot route to the site server The client cannot resolve DNS for the site server There is no network access account configured (other reason, stated in the smsts.log) The first paragraph above should help you get command support testing enabled, and from there, you should be able to find your smsts.log. This will be your best bet in helping you to discover what is going wrong. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  9. Did you duplicate another task sequence, or build a new one? Did you select a 64-bit boot image instead of a 32-bit boot image? What is the error you're getting when the task sequence fails? Have you checked the smsts.log to see what's going on? You'll want to enable command prompt support in your boot images, which will allow you to find and open smsts.log. Depending on where you are at in the task sequence, it will be in different locations. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  10. I'm not sure what you mean. Which boot method do you want to use? PXE, USB flash drives, optical media, and a WinPE WIM installed on the local hard drive are all options. Can you please clarify what you are after? Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  11. I'm not sure what you mean. Which boot method do you want to use? PXE, USB flash drives, optical media, and a WinPE WIM installed on the local hard drive are all options. Can you please clarify what you are after? Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  12. Are the clients showing that they are assigned to a site? It sounds like they client is getting installed, but they are failing to perform site assignment, which results in a DDR not getting created, which means that they won't show up as objects in the console. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  13. +1 vote for build & capture base image on virtual hardware. VMware Workstation works perfectly for this. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  14. What is the problem that you're experiencing? Are you getting error messages? Need more specifics. By the way, you've got a massive task sequence there, considering the relatively simple task at hand! I would recommend taking the time to engineer a task sequence from the ground up that has only the steps that you specifically need in it. This isn't something that is done overnight. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
  15. Open PowerShell and run this command to get the build number: $Site = Get-CimInstance -Namespace root\sms\site_LAB -ClassName SMS_Site; $Site | Select-Object -Property BuildNumber,SiteCode; Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86
×
×
  • Create New...