Came across the following TechNet article which lists all the current Lync Powershell cmdlets along with a description of what they do.
http://blogs.technet.com/b/csps/archive/2010/07/16/refallcmdlets.aspx
NeilC
Just came across this really interesting and useful article on using secondary pools for Lync resilience and the best way of getting clients to pick up the secondary pool in the event of failure.
Happy reading.
NeilC
To create a collection like this we need to setup a collection based on a query, the attributes that we will use will be..
Attribute Class: System Resource
Attribute: System OU Name
The Operator can be set to : is equal to
Values should be available when you click the value button.
If the values are not populated chances are is that the Active Directory System Group Discovery has either not been set or the OU you require has not been specified.
Enable the group discovery and add a Custom LDAP query to the OU/OUs in question, initiate a scan by selecting “Run discovery as soon as possible” in the polling schedule tab, you can monitor the progress of this in the adsysgrp.log
After this complete you should see the SMS table System_System_OU_Name_ARR table in the SCCM database will populate with data in the System_OU_Name0 column of the database.
The OU’s will now populate for the containers or domain you specified in the AD System Group Discovery LDAP queries.
Select the OU from the list, alternatively you can specify using the following query;
select * from SMS_R_System where SMS_R_System.SystemOUName = "<FQDNDomain>/<OUName>"
John Riseam
System Center Consultant
Risual Ltd
To activate Office at installation time can be the preferred method when installing operating system via SCCM in a production environment. You would expect this to be an option in the Office Customisation Tool but after much searching you may find that it doesn’t appear as a listed item.
You need to add the following entry into the Modify Setup properties giving the Property Name AUTO_ACTIVATE and a Value of 1 this will make sure that you copy of office gets registered and negates the requirement of a manual step after installation.
John Riseam
System Center Consultant
Risual Ltd
With R3 being the latest feature pack to be released and the first to be labelled R3 in Microsoft’s history, along with functional improvements it brings its own challenges. You can roll out the hotfix to existing agents via the standard software distribution method, however I like to deploy my SCCM Clients in my task sequences fully patched. Also if you want to distribute the SCCM console into your build it become a bit of an issue as the R3 components require the hotfix to complete the installer.
If you add the hotfix to the SCCM task sequence as a software install or install it via a script it will break the Task Sequence as it stops the Winmgmt service which has to be running.
To add the patch we need to edit the “Setup Windows and ConfigMgr” step in the task sequence and add the following line to the Installation properties field.
PATCH=”C:\_SMSTaskSequence\OSD\<PackageID>\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp”
The package ID must be the ID of the Config Manager Client that is been used in the deployment and not the hotfix package ID, also make sure that the package has been updated to reflect the hotfix folder in <SCCMInstallDir>\Client\i386\hotfix. This is created during the initial R3 update when run on the site server if the option was selected to create the KB977384 – Advanced Client Patch Install.
You can confirm this during a test installation once the SCCM client is installed hit F8 if enabled in WinPE and run C:\Windows\System32\CCM\SMSCFGRC.CPL and check the ConfigMgr Client Version it should be 4.00.6487.2157
John Riseam
System Center Consultant
Risual Ltd
