June 2008 - Posts
As I promised, I will share this end to end ConfigMgr SP1 setup guide. This is for fresh install not for upgrade. You could literally get your ConfigMgr environment up and running within hours! This is for the core infrastructure and you could extend the hierarchy according to your environment.
Download Doc
Recently I am focused on to design and implement ConfigMgr for our company. Unfortunately there are no native support for PowerShell in ConfigMgr yet. So if you see I am “slacking”, you know why! 
But I am finishing up a ConfigMgr SP1 setup guide and will share it soon.
Lately our team received a lot requests to add new DNS records for our testing web server, I am getting tired to add A record in DNS manually for those Host headers in IIS. Here is what I come up
#xyz is dns servername
$A = [wmiclass]"\\xyz\root\MicrosoftDNS:MicrosoftDNS_AType"
$DNSServer = "xyz.R-test.com"
$Zone = "R-Test.com"
$class = 1
$TTL = 3600
#This is your web server IP Address
$IPAddress = "192.168.1.88"
$Sites = Get-content WebSites.txt
Foreach ($Site in $Sites)
{
$A.CreateInstanceFromPropertyData($DNSserver, $zone, $Site, $class, $ttl, $IPAddress)
}
The WebSites.txt is something look like this:
whatever1.R-test.comwhatever2.R-test.comwhatever3.R-test.com
whatever4.R-test.com
…
If whateverx already has a DNS A record, you will get something like this:
Exception calling "CreateInstanceFromPropertyData" : "Generic failure "
At C:\Documents and Settings\Administrator.RELATED-TEST\My Documents\AddDNSARecords.ps1:13 cha
+ $A.CreateInstanceFromPropertyData( <<<< $DNSserver, $zone,$Site, $class, $ttl, $IPAddress)
Thanks Richard Siddaway for his post Here
The word is out, at the TechEd 2008 for IT Professional (June 10–13, 2008),
PowerGUI has received the highest award – The breakthrough product of the show. If you haven’t tried already, You can download from the link above. Trust me, you sure will like it! Kudos to Dimitry and his team!
If you are a fan of the Sysinternals tools, check out the beta of
Sysinternals Live , a service that can let you execute Sysinternals tools directly from the Web without hunting for or manuallly downloading them. Simply enter a tool’s Sysinternals Live path into Windows Explorer, or at the command prompt as \\live.sysinternals.com\tools\,toolname>, or view the entire Sysinternals Live tools directory in a browser.
I am working on to setup a new ConfigMgr (SCCM) hierarchy. The first hurdle I have to overcome is once I have the central site (RP and SUP) and the main primary site setup. The standard sender is automatically created for me and all I need is to create the addresses for each site as detailed in How to Create Configuration Manager Site Addresses
So end of the story? Not quite, at least for me.
To create a Configuration Manager site address
-
In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Addresses.
-
Right-click Addresses and then click New.
-
Select the type of address that you want to create to start the appropriate New Address Wizard.
-
To finish installing the address, complete the General, Schedule, and Rate Limits pages of the New Address Wizard.
As this is brand new setup – there is nothing to select when you click the down arrow next to Destination site code. Actually we do can type with a list box even though this is not really new but somehow that down arrow hard coded my brain and make me believe I can only “select” not type. That almost cost me a PSS call!
Once I type in the destination code and type in the Site Server name (if the site you need to connect is 901 on server USNYSCCM01, the destination code should be 901 and the Site server name should be USNYSCCM01!). All I need to do is to wait until the the address from 901 – (Unknown) to 901 – Headquarter.
There is one more thing that bothers me but I don’t know if it is by design. On the central site, I can see the above change but on the primary site console. it stays as 900 – (Unknown). But if you look at it on the console in central site – it indeed change to 900 – Central Site!
The bottom line is I know it is working!