Is it possible to just download the prerequsites on forehand if you dont have Internet access on the server where you intend to install Configuration Manager.
Yes you can , you need to use the command without the quotes “MEDIAPATH:SMSSETUPBINI386setup.exe /download drive:path”
Make sure the folder you download to is created before you execute the command otherwise it will not launch.
I just got the question on what rights the domain join account needs. So here it is.
First of all you need to create an account for it in this example I named min svc-sccm-domainjoin and then locate the OU where your computer accounts will reside in. And then right click on it and set the security rights.
First you need to set the following rights on the OU and with the setting Apply to: This object and all descendant objects.
- Create Computer Object
- Delete Computer Object
After that you need to add the following rights with the setting apply to: Descendant Computer objects.
- Read All Properties
- Write All Properties
- Read Permissions
- Modify Permissions
- Change Password
- Reset Password
- Validated write to DNS host name
- Validated write to service princ
With Service Pack 2 of Configuration Manager it is no longer required to provide a certificate to synchronize the Asset Intelligence Catalog with Microsoft, it is now builtin. Although when you install it it may cause some confusion.
So when you install the Asset Intelligence Sync Point role it still asks for a certificate, but its just to ignore that page and click next to install the role. Earlier it was required to have a certificate and with SP2 that has been removed.
So when you hit this page in the wizard just click next.
After you have installed the role you can look in these three log files AIUSMSI.log , AIUSSetup.log, aikbmgrlog and AIUpdateSvc.log to see that everything is working as intended. http://technet.microsoft.com/en-us/library/cc161940.aspx
Microsoft just released information about System Center Configuration Manager R3 you can read more about it here. Its an very exciting release.
http://blogs.technet.com/systemcenter/archive/2009/09/08/announcing-system-center-configuration-manager-2007-r3.aspx
When using software Updates with Configuration Manager you may want to deploy a new WU Agent to your machines for several reasons. WUA might cause all kinds of problems with client scanning and deployment. So my recommendation is to keep the WU Agent up to date. It’s not all times the clients update the agent by itself so therefore you will see a manual way of deploying it in this article.
- Download the wuredist.cab from this url http://update.microsoft.com/redist/wuredist.cab
- When you have downloaded the file you need to extract and open the wuredist.xml file.
- In the file you should look for the download source for the different platform agents. Below I have listed the current once but it will change as time go by.
- After that you need to create a package with the source files and distribute it to your DPs.
- You also need to specify a program for the package I use this syntax for my x86 platform as I don’t want to force a restart and hide it from the end user.
WindowsUpdateAgent30-x86.exe /WUForce /quiet /norestart
- You also need to create a collection for your machines to target an example query could be the following. With this query all active non obsolete clients that doesn’t have WUA 7.2.6001.788 will be listed. Make sure you have not like or like otherwise the version handling won’t work.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_WINDOWSUPDATEAGENTVERSION on SMS_G_System_WINDOWSUPDATEAGENTVERSION.ResourceID = SMS_R_System.ResourceId where SMS_G_System_WINDOWSUPDATEAGENTVERSION.Version not like "7.2.6001.788" and SMS_R_System.Client = 1 and SMS_R_System.Obsolete != 1 and SMS_R_System.Active = 1
7. After this you need to create a advertisement to deploy to the collection and follow your deployment in the reports.
References
Http://support.microsoft.com/kb/949104
http://msdn.microsoft.com/en-us/library/aa387285(VS.85).aspx
It is now around 3 years since beta 1 was released, and it has been an interesting journey to follow. After 3 years we are now at SP1 and the optional upgrade R2. Service Pack 2 is soon to be released. The pain the joy and the happiness I have found working with Configuration Manager during this time is hard to describe but there is something there that keeps me going.
A few milestones in the evolution of Configuration Manager, if I have gotten some dates wrong please correct me.
- June – 06 Beta 1 was released
- February – 07 Beta 2
- July – 07 Release Candidate 1
- November – 07 RTM (Released to Manufacturing)
- February – 08 SP1 and R2 RC
- May – 08 SP1 RTM
- September – 08 R2 RTM
- June – 09 SP2 Beta
So what did with we get with the different releases?
RTM
Some new major new functions in Configuration Manager compared to SMS 2003 are
- Operating System Deployment with Task Sequencing
- Improved Software Update functionality based on WSUS
- A solid Desired Configuration Management function for compliance and detection of Management Drift
- Maintenance Windows
For the full details please go here.
http://technet.microsoft.com/en-us/library/bb680807.aspx
SP1
Configuration Manager 2007 SP1 came out in May 2008 and it gave us several new functions.
- Intel vPro integration also called Out of Band Management
- Improved Asset intelligence new reports and a new engine for Asset Intelligence
- Support for Windows Vista SP1 and Windows Server 2008
You can get the full details here.
http://technet.microsoft.com/en-us/library/cc161901.aspx
R2
And next to come was R2 is in September 2008, with the R2 release of Configuration Manager new functions where introduced
- App-V integration so that we could deploy App-C applications without the App-V infrastructure. (Formerly known as Softgrid)
- A Client Health Status was released to help in the process of finding unhealthy clients.
- SQL Reporting Services Integration where introduced to get away from the old ASP based reports.
- The Operating System Deployment where extended to support unknown computers and the ability to run a task sequence step for command line as another user then the local system
- In combination with Windows 2008 it is now also possible to use Multicast deployments.
You can get the full details here.
http://technet.microsoft.com/en-us/library/cc161883.aspx
SP2
As I wrote earlier SP2 is the next to be released a maximum 90 Days after RTM of Windows 7. But what does really Service Pack 2 give us? As you may understand already the main objective is to get support for Windows 7. But there are also some other features. This information was released at Microsoft Management Summit in Las Vegas
- Windows 7 and Windows 2008 R2 support
- Windows Vista SP2 support
- 36 integrated QFE
- Update to Management Pack for 64-bit OS’s – SP2 will ship 64-bit perf counters
- Remote control added in for (x64 XP and Sever 2003)
- Multi-select and delete driver catalog drivers from the console
- Better feedback on AD extension success / failure
- Windows 7, Windows Server 2k8 R2 supported as clients
- All SCCM server roles fully supported on Server 2k8 R2
- P2P support for Win7 (BranchCache)
- USMT 4.0 support for OSD
- Intel Active Management Technology (iAMT)
Beyond SP2 what can we expect?
Microsoft is currently working on the next version of Config Manager and according to the roadmap we could expect that coming in 2011. If you are planning your new Config Mgr environment there are some considerations you should consider already now I have listed them below.
Image Source: techlog.nl
- 64 bit only for site systems expect Branch DP and Windows 2003
- SQL 2008 and 64bit only
- Some roles may require Windows 2008 R2
- For reporting the only reporting engine will be SQL Reporting Services
- SQL Replication will most likely be used for more things so get familiar with it.
As the world is changing things will move against a more user centric world where the user is centric. We are getting more and more mobile and this will be a big focus in the next version. Delivering applications in different ways depending on where we work from etc.
If you are interested in running SP2 in a TAP (Technology Adotion Program) It is high time to nominate oyourself or someone else for it. The biggest driver is the support and integation with Windows 2008 R2 and Windows 7.
You can read more about it here at the Config Mgr Team Blog
I highly suggest early adotopers of technology to sign up if you already are running Config Mgr.
Well the case is that Configuration Manager doesnt support patches that require User input and isnt therefor replicated to the Configuration Manager environment. So theese updates need to be deployed in another way, although many customers patch clusters manually so it is not a problem for them, but you wont see the compliance status for thoose patches either. So Config Mgr admins out there keep an eye on this´so you wont miss important patches for your environment.
To find updates that cant be installed with Configuration Manager you can query your SUSDB for patches that require User Input.
USE SUSDB
SELECT SecuirtyBulletin, DefaultTitle, KnowledgebaseArticle, InstallationCanRequestUserInput
FROM PUBLIC_VIEWS.vUpdate Where InstallationCanRequestUserInput = 1
Source of material: http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/a4ea7e76-0589-4eb4-a31f-a17b6ab9ea41
Config Mgr, ConfigMgr 2007 | stesch | 
December 28, 2009 21:52 | 
Comments (0) 
Subscribe 