SMS to SCCM Auto Migration Script

SMS to SCCM Auto Migration Script

 

Copy.bat

 

xcopy /y ccmsetup.exe c:\windows\temp\
xcopy /y ccmclean.exe c:\windows\temp\
xcopy /y install.bat c:\windows\temp\
schtasks /CREATE /SC MINUTE /mo 90 /TN Migration /TR "C:\windows\temp\install.bat" /RU SYSTEM
schtasks /CREATE /SC MINUTO /mo 90 /TN Migration /TR "C:\windows\temp\install.bat" /RU SYSTEM

 

 

Install.bat

 

C:\windows\temp\ccmclean.exe /client /q
C:\windows\temp\Ccmsetup.exe /mp:ServerName SMSSITECODE=Sitecode

SCHTASKS /delete /TN Migration /F

 

 

Advertise the Copy.bat then automatically clients will installing the sccm

WMI / WQL Easy Editor

This is a good tool

http://wqlqueryrunner.codeplex.com/

 

 

Project Description
WQL Query Runner is (or would be) a tool for WMI SQL query testing.
There are different types of WQL queries. My plan is to support creating all of them, and the first type for which I decided to add support are WQL event queries.
WMI is the Microsoft implementation of WBEM, the industry initiative for computer and network management. It allows you to manage most computer assets in a uniform way. There are several APIs that you can use to access WMI, and most of them utilize WQL queries. WQL is a query language derived from SQL - you can think of it as a simplified SQL language.
The main difficulty when creating WQL queries is not its syntax, but choosing the right WMI objects to SELECT data from and the goal of the utility is to make constructing and testing WQL queries easier.
There are different types of WQL queries, and my plan is to support creating all of them, and the first for which I decided to add support are WQL event queries. The utility provides a way to enter and test event WQL queries locally and also features a wizard that attempts to walk you through all WQL event query elements.

As you can see, this is my first .Net project. I am a system administrator, not a developer, so creating this application involved a lot of learning with little success. So why did I decide to start this? In short, because noone else did. There are several tools out there that help you work with WMI, like WMI tester (wbemtest.exe) that comes with Windows, WMI Tools (a free Microsoft download), WMI Scriptomatic (also a free download from the Microsoft Scripting guys) and WMI Code Creator, but none of these tools concentrate solely on WQL queries - WMI Tester and WMI Tools facilitate browsing the WMI schema, and Scriptomatic and Wmi Code Creator allow you to generate VBScript, C# (and other) code.
It's also been great fun. So until someone that really knows what he's doing starts a similar project, I will continue to work on this one.
2011-02-19
Added a new form to the project that allows you to run ordinary (data) WQL queries. The form is called WQL Query Editor and is similar to the old SQL Server 2000 Query Analyzer.

You can browse available WMI namespaces and classes on the local computer using the TreeView control on the right hand side and execute queries entered in the upper RichTextBox. The results are shown in the lower RichTextBox and can also be viewed in a DataGridView control.
Query Editor can be started from the main window context menu:

or by using a command line switch:
WqlQueryRunner.exe queryeditor
WQL Query Editor takes a couple of seconds to show because it enumerates all available WMI namespace when it starts.

SCCM State ID’s from Client end error (Focused on Patching )

TopicType	StateID	StateName	StateDescription
300	0	Compliance state unknown	Compliance state unknown
300	1	Compliant	Compliant
300	2	Non-compliant	Non-compliant
300	3	Conflict detected	Conflict detected
301	0	Enforcement state unknown	Enforcement state unknown
301	1	Installing update(s)	Installing update(s)
301	2	Waiting for restart	Waiting for restart
301	3	Waiting for another installation to complete	Waiting for another installation to complete
301	4	Successfully installed update(s)	Successfully installed update(s)
301	5	Pending system restart	Pending system restart
301	6	Failed to install update(s)	Failed to install update(s)
301	7	Downloading update(s)	Downloading update(s)
301	8	Downloaded update(s)	Downloaded update(s)
301	9	Failed to download update(s)	Failed to download update(s)
301	10	Waiting for maintenance window before installing	Waiting for maintenance window before installing
302	0	Evaluation state unknown	Evaluation state unknown
302	1	Evaluation activated	Evaluation activated
302	2	Evaluation succeeded	Evaluation succeeded
302	3	Evaluation failed	Evaluation failed
400	0	Detection state unknown	Detection state unknown
400	1	Not Required	Not Required
400	2	Not Detected	Not Detected
400	3	Detected	Detected
401	0	Compliance state unknown	Compliance state unknown
401	1	Compliant	Compliant
401	2	Non-Compliant	Non-Compliant
401	3	Conflict Detected	Conflict Detected
401	4	Error	Error
402	0	Enforcement state unknown	Enforcement state unknown
402	1	Enforcement started	Enforcement started
402	2	Enforcement waiting for content	Enforcement waiting for content
402	3	Waiting for another installation to complete	Waiting for another installation to complete
402	4	Waiting for maintenance window before installing	Waiting for maintenance window before installing
402	5	Restart required before installing	Restart required before installing
402	6	General failure	General failure
402	7	Pending installation	Pending installation
402	8	Installing update	Installing update
402	9	Pending system restart	Pending system restart
402	10	Successfully installed update	Successfully installed update
402	11	Failed to install update	Failed to install update
402	12	Downloading update	Downloading update
402	13	Downloaded update	Downloaded update
402	14	Failed to download update	Failed to download update
500	0	Detection state unknown	Detection state unknown
500	1	Update is not required	Update is not required
500	2	Update is required	Update is required
500	3	Update is installed	Update is installed
501	0	Scan state unknown	Scan state unknown
501	1	Scan is waiting for content	Scan is waiting for content
501	2	Scan is running	Scan is running
501	3	Scan completed	Scan completed
501	4	Scan is pending retry	Scan is pending retry
501	5	Scan failed	Scan failed
501	6	Scan completed with errors	Scan completed with errors
501	7	SMS 2003 client	SMS 2003 client
800	100	Client deployment started.	Client deployment started.
800	301	Unknown client deployment failure.	Unknown client deployment failure.
800	302	Failed to create the ccmsetup service.	Failed to create the ccmsetup service.
800	303	Failed to delete the ccmsetup service.	Failed to delete the ccmsetup service.
800	304	Cannot install over embedded OS with File Based Write Filter (FBWF) enabled on system drive.	Cannot install over embedded OS with File Based Write Filter (FBWF) enabled on system drive.
800	305	Native security mode is invalid on Windows 2000.	Native security mode is invalid on Windows 2000.
800	306	Failed to start ccmsetup download process.	Failed to start ccmsetup download process.
800	307	Invalid ccmsetup command line:	Invalid ccmsetup command line:
800	308	Failed to download file over WINHTTP at address:	Failed to download file over WINHTTP at address:
800	309	Failed to download files through BITS at address:	Failed to download files through BITS at address:
800	310	Failed to install BITS version:	Failed to install BITS version:
800	311	Can't verify that prerequisite file is MS signed:	Can't verify that prerequisite file is MS signed:
800	312	Failed to copy file because disk is full.	Failed to copy file because disk is full.
800	313	Client.msi installation failed with MSI error:	Client.msi installation failed with MSI error:
800	314	Failed to load ccmsetup.xml manifest file.	Failed to load ccmsetup.xml manifest file.
800	315	Failed to obtain client certificate.	Failed to obtain client certificate.
800	316	Prerequisite file is not MS signed:	Prerequisite file is not MS signed:
800	317	A reboot is required to continue installation.	A reboot is required to continue installation.
800	318	Can't install the client on the MP because the MP and client versions don't match.	Can't install the client on the MP because the MP and client versions don't match.
800	319	The operating system or service pack is not supported.	The operating system or service pack is not supported.
800	400	Client deployment succeeded.	Client deployment succeeded.
800	500	Client assignment started.	Client assignment started.
800	601	Unknown client assignment failure.	Unknown client assignment failure.
800	602	The following site code is invalid:	The following site code is invalid:
800	603	Failed to assign to MP:	Failed to assign to MP:
800	604	Failed to discover default management point.	Failed to discover default management point.
800	605	Failed to download site signing certificate.	Failed to download site signing certificate.
800	606	Failed to auto discover site code.	Failed to auto discover site code.
800	607	Site assignment failed. Client version is higher than the site version.	Site assignment failed. Client version is higher than the site version.
800	608	Failed to get Site Version from AD and SLP.	Failed to get Site Version from AD and SLP.
800	609	Failed to get Client Version.	Failed to get Client Version.
800	700	Client assignment succeeded.	Client assignment succeeded.
1000	1	Client is successfully communicating with the Management Point	Client is successfully communicating with the Management Point
1000	2	Client is failing to communicate with the Management Point	Client is failing to communicate with the Management Point
1001	1	Client is successfully retrieving a certificate from the local certificate store	Client is successfully retrieving a certificate from the local certificate store
1001	2	Client is failing to retrieve a certificate from the local certificate store	Client is failing to retrieve a certificate from the local certificate store
1100	1	Client is not ready for Native Mode	Client is not ready for Native Mode
1100	2	Client is ready for Native Mode	Client is ready for Native Mode

Move SCCM Database to remote SQL server

 

a. Back up the site database on the current site database server and restore it on the new site database server computer using the SQL Server Management Studio.

b. Ensure the primary site server computer account has administrative privileges over the new site database server computer.

c. Close any open Configuration Manager console connections to the site server.

d. On the primary site server computer, use the hierarchy maintenance tool (Preinst.exe) to stop all site services with the following command: Preinst /stopsite.

e. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup, or navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.

f. Click Next on the Configuration Manager Setup Wizard Welcome page.

g. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.

h. Select Modify SQL Server configuration on the Configuration Manager Setup Wizard Site Maintenance page.

i. Enter the appropriate SQL Server name and instance (if applicable) for the new site database server as well as the site database name on the Configuration Manager Setup Wizard SQL Server Configuration page.

j. Configuration Manager Setup performs the SQL Server configuration process.

k. Restart the primary site server computer, and verify the site is functioning normally.

SCCM Accounts I can : Below are the accounts used in SCCM

1.       AMT Provisioning and Discovery Account

 

a.       Describes the function, creation, maintenance, and security best practices for the AMT Provisioning and Discovery Account.

 

2.       AMT Remote Admin Account

 

a.       Describes the function, creation, maintenance, and security best practices for the AMT Remote Admin Account.

 

3.       AMT User Accounts

 

a.       Describes the function, creation, maintenance, and security best practices for the AMT User Accounts.

 

4.       Capture Operating System Image Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Capture Operating System Image account.

 

5.       Client Push Installation Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Client Push Installation account.

 

6.       Health State Reference Publishing Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Health State Reference Publishing account.

 

7.       Health State Reference Querying Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Health State Reference Querying account.

 

8.       Management Point Database Connection Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Management Point Database Connection account.

 

9.       MEBx Account

 

a.       Describes the function, creation, maintenance, and security best practices for the MEBx Account.

 

10.   Multicast Service Point Connection Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Multicast Database Connection account.

 

11.   Network Access Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Network Access account.

 

12.   Package Access Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Package Access account.

 

13.   PXE Service Point Database Connection Account

 

a.       Describes the function, creation, maintenance, and security best practices for the PXE Service Point Database Connection account.

 

14.   RAS Sender Phone Book Account

 

a.       Describes the function, creation, maintenance, and security best practices for the RAS Sender Phone Book account.

 

15.   Remote Tools Permitted Viewer Accounts

 

a.       Describes the function, creation, maintenance, and security best practices for the Remote Tools Permitted Viewer accounts.

 

16.   Server Locator Point Database Connection Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Server Locator Point Database Connection account.

 

17.   Site Address Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Site Address account.

 

18.   Site System Installation Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Site System Installation account.

 

19.   Software Update Point Connection Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Software Update Point Connection account.

 

20.   Software Update Point Proxy Server Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Software Update Point Proxy Server account.

 

21.   Task Sequence Editor Domain Joining Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Task Sequence Editor Domain Joining account.

 

22.   Task Sequence Editor Network Folder Connection Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Task Sequence Editor Network Folder Connection account.

 

23.   Task Sequence Run As Account

 

a.       Describes the function, creation, maintenance, and security best practices for the Task Sequence Run As account.

Replace the Hardware for a Secondary Site

One way to replace the hardware for a Secondary Site

from Sherry ==> http://myitforum.com/cs2/blogs/skissinger/archive/2008/07/09/one-way-to-replace-the-hardware-for-a-secondary-site.aspx

Tools needed:

1. Preinst.exe from SMS 2003 Toolkit 2 http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.mspx

2. PreLoadPkgonSite also from SMS 2003 Toolkit 2

3. CloneDP, installed (pre-req of .Net 2) http://sourceforge.net/projects/smsclonedp/

4. Script or method to enumerate .pkg files in X:\smspkg

5. MPTroubleshooter also from SMS2003 Toolkit 2

Resources needed locally on the new server:

1. SMS 2003 Setup files

2. If secondary is to be a proxy MP, setup files for the Operating System

3. Restored or copied from old server, X:\smspkg

4. Restored or copied from old server, X:\smspkgx$ **  (Any steps marked with a ** are optional, see footnote)

Resources needed remotely:

Rights and ability to remote into any primary sites above the secondary site to be replaced.

Timeline - There are 4 time frames

1. Tasks that can done before the new hardware is shipped to the destination; but could also be done once hardware arrives at new location.

2. Tasks done after the new hardware has arrived.

3. Work done after SMS 2003 reinstalled

4. Follow up the next day.

Prior to shipping hardware

1. From a local Distribution Point, copy \\otherserver\x$\smspkg to x:\smspkg

2. From a local Distribution Point, copy \\otherserver\x$\smspkgx$ to x:\smspkgx$ **

3. Copy SMS 2003 setup files to x:\SMSTools\setup

4. Copy PreloadPkgonSite.exe to x:\SMSTools

5. Copy PreloadBuild.vbs to x:\SMSTools

The above steps could also be done once the hardware arrives at the destination, or restored from backup--if you backup your secondary (which we don't normally)

Hardware arrived

1. Optional: if you copied smspkg & smspkgx$ over from ServerOld to ServerNew a significant time ago, you may want to do a Delta copy just before starting.  Otherwise, if you preloadpkgonsite of an old version of a pkg file, those packages will need to be re-replicated from the parent.

2. On Current Server, Disable the SMS Services so they do not launch automatically following a reboot.

3. Rename current Server to ServerName_OLD, change IP address from static to dhcp. Reboot.

4. On new hardware, rename to ServerName, change IP from dhcp to static. Reboot.

5. Install IIS with BITS. If IIS had been installed under the old name, uninstall IIS, then reinstall IIS. This is to ensure the iis usernames are defined correctly.

6. Follow the EdNet instructions for removing the Secondary Site from the Primary Site(s) databases, and deleting any jobs. These instructions use the preinst.exe toolkit tool at the Primary Site, and Query Analyzer. (http://www.myitforum.com/articles/1/view.asp?id=5355)

7. Remove the SMS entries for the server in Active Directory for the server itself, and for the MP record. (in the OU System\System Management, SMS-Site-xxx, and SMS-MP-xxx-ServerName)
   

8. At the Primary Site(s), remove the Standard Sender Address for the secondary site.  Wait a minute or so.

9. At the Primary Sites(s), create a new Standard Sender Address for the secondary site.
   

10. At the secondary site, unshare smspkge$ & rename to smspkge_old (you’ll move files later)**

11. At the secondary site, install SMS from smstools\...\setup.exe, Advanced Security, Remote Tools enabled.

12. Monitor sms\logs\*.log files for errors

13. Monitor Active Directory Users and Computers, the OU System/System Management, for SMS-Site-Rxx to appear.

14. At the direct Primary site, refresh Site hierarchy occasionally. When you see the site reappear, configure boundaries, Addresses, client Agents, Discovery Methods. Configure Site Systems to be a Management Point, and Distribution Point with BITS.

15. At the secondary site, monitor sms\logs\mpsetup.log for success/failure.
    If failed, stop and troubleshoot. Multiple problems can occur with this step. Too many to detail here.
    If success, run the MP troubleshooter to verify.

SMS Reinstalled

1. Push down 1 (smallish) package. Monitor the Secondary Site recreating smspkge$ share, and putting the new package in there.

2. Highlight all the folders in smspkge_old, and verify the ntfs permissions match what they should be in the new smspkge$. Reset as necessary. Once satisfied permissions are correct, Move all the folders (except the new one you just had rebuilt) to the new smspkge$. You can delete smspkge_old when done (there should only be 1 folder left). **

3. At the secondary, go to a command prompt. CD to x:\smspkg Pick 1 package. Type in x:\smstools\preloadpkgonsite PackageID (without the .pkg extension, i.e., x:\smstools\preloadpkgonsite TST00012)

4. A success message looks like this:
   Forward package status for pkg C0100012 to site C01
   ****** Successfully set the Compressed Package Path on this site ******
   ****** Successfully forwarded the information up the hierarchy ******
   If you got a different message (a failure message), try a different package. If all Packages fail, you may need to check that *.pkg are all Read-only.

5. Following the success message, monitor distmgr.log on the Secondary to confirm that package's info has been sent.

6. At the Central Site, add the (new) Secondary site distribution point to that 1 package.

7. Monitor Sender.log at the server(s). Monitor Package Status at the Primary Site server(s).

8. Once you are satisfied the process works, use this script to create a batch file in e:\smspkg to run preloadpkgonsite against all the .pkg files.

9. Edit: instead of steps 9, 10, 11; check out Marcus Oh's blog entry on using PreloadPkgOnSite
   Create a preloadbuild.vbs file with the below in e:\smstools. Then start, run wscript e:\smstools\preloadbuild.vbs
   The script (correct the variables for your environment/server; the E: drive may not be correct for you):
   set fso = wscript.CreateObject("Scripting.FileSystemObject")
   set fo = fso.getFolder("e:\smspkg")
   set fc = fo.Files
   set TheFile = fso.createtextfile("e:\smspkg\preload.bat",True)
   For each file in fc
   TheArray = Split(file,"\", -1, 1)
   StrNameToLoad = Left(TheArray(2),8)
   theFile.writeline "e:\smstools\preloadpkgonsite " & strNameToLoad & " >> e:\smstools\preload1.txt"
   next
   TheFile.Close

10. Now that you have a e:\smspkg\preload.bat, go to a cmd prompt, and switch to e:\smspkg. Type in preload.bat, and wait.

11. When it is done, open up e:\smstools\preload1.txt and verify the majority of the entries are “successfully forwarded”. It’s OK if there are a few errors, but if all are errors, there may be a problem.

12. Watch distmgr.log on the secondary; wait for it to complete sending up packages (how long depends upon how many packages you have, this can take quite a while for me).

13. After waiting, add the new DP to a package at the Central Site, and confirm via watching sender.log that the entire package is indeed NOT being replicated downward.

14. Once you’ve confirmed that, run CloneDP, and pick a similar Secondary Site to Clone to the new one. It may take quite a while for CloneDP to go through the entire list of packages to Clone. This is normal; just wait.

CloneDP usage

1. Launch

2. SMS Primary Site Server = your Primary Site Server that has the packages, OK

3. Select an existing Distribution Point, pick a Site Code, a DP, drag & drop the server name to the Packages Source List

4. Select Destination of the new site

5. Click “Assign Packages to DP”.

6. This is the point where "waiting" begins; or the "go to bed and check on it in the morning" step!

Follow up the Next day

1. The following day, check Package Status. For any packages that appear not to have worked, you may need to update all Distribution Points for that 1 package.

** Why are these optional?  In our environment, if for some reason there is an "emergency" software installation which may need to occur before a Secondary can be fully rebuilt, the local technicians can browse to the smspkgx$ share, the folder, and manually install software.  For that reason, we copy over the smspkgx$ folders, etc.  As SMS unpacks the .pkg files into smspkgx$, the folders are replaced.

Distribution Point Update Vs Refresh

Choose Between Updating and Refreshing a Package

Applies To: System Center Configuration Manager 2007 only

Updating and refreshing Microsoft System Center Configuration Manager 2007 packages are two different operations. Use the following table to help decide when to update and when to refresh a package.

 

Criterion	Package Update	Package Refresh
Use when	You make a modification to the package source, such as adding, changing, or deleting a file or folder.	You need to repair a package at a specific distribution point.
What it does	Builds a new, complete, compressed package file and a delta compressed package file from the updated package source files. The delta file is passed to all distribution points.	Recopies the compressed package from the local site server to the distribution point but does not copy files from the package source.
Resets access control list (ACL)?	No.	Yes, if you have made changes to the Package Access Accounts.
Resets the Virtual Directory?	Yes, if you have enabled or disabled BITS on the distribution point since the last package update.	Yes, if you have enabled or disabled BITS on the distribution point since the last package refresh.
Updates the package source version?	Yes.	No.
Increments package version in client policy?	Yes.	No.

Manage DP wizard ==>using Refresh the package?--Delete and recreate the package ,does not change source version.

right click Update ==>Distribution Point -Change source version and copy the changed source.(Delta change)

 

 

more ==>http://technet.microsoft.com/en-us/library/bb892806.aspx

LAB Setup

Hey below are the LAB Details to setup and meet the real time.

Total RAM Required is 6.2 GB + Base OS as 1 GB

 

 

 

 

--------------------------------------------------------------------------------------------------------------------------------
The above same posting as Excel work Book also

--------------------------------------------------------------------------------------------------------------------------------

 

	HYD Site Systems Details for easy config
OS	Role	RAM	System Name	IP address	Subnet Mask	Default Gateway	DNS Srv 1	DNS Srv 2
2008 R2	DC	256 MB	inhydtcs-dc01	10.0.0.1	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
2008 R2	Exchange	512 MB	inhydtcs-ex01	10.0.0.2	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
2008 R2	Central Site	700 MB	inhydtcs-cm01	10.0.0.3	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
2008 R2	Central SQL	700 MB	inhydtcs-sq01	10.0.0.4	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
2008 R2	Primary Site	1 GB	inhydtcs-cm02	10.0.0.5	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
XP	Client Xp1	128 MB	intcshyd-WS01	10.0.0.6	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
XP	Client 2	128 MB	intcshyd-WS02	10.0.0.7	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
windows 7	Client 3	512 MB	intcshyd-WS03	10.0.0.8	255.255.0.0	10.0.0.100	10.0.0.1	172.0.0.1
	BLR Site Systems Details for easy config
OS	Role		System Name	IP address	Subnet Mask	Default Gateway	DNS Srv 1	DNS Srv 2
2008 R2	ADC	256 MB	Inblrtcs-adc1	172.0.0.1	255.255.255.0.	172.0.0.100	172.0.0.1	10.0.0.1
2008 R2	Primary Site	1 GB	inblrtcs-cm03	172.0.0.2	255.255.255.0.	172.0.0.100	172.0.0.1	10.0.0.1
XP	Client Xp1	128 MB	intcsblr-WS01	172.0.0.3	255.255.255.0.	172.0.0.100	172.0.0.1	10.0.0.1
XP	Client 2	128 MB	intcsblr-WS02	172.0.0.4	255.255.255.0.	172.0.0.100	172.0.0.1	10.0.0.1
windows 7	Client 3	512 MB	intcsblr-WS03	172.0.0.5	255.255.255.0.	172.0.0.100	172.0.0.1	10.0.0.1
	Router Configuration Details - Should have two network cards
OS	Role		System Name	IP address	Subnet Mask	Default Gateway	DNS Srv 1	DNS Srv 2
Windows 2003	Router	200 MB	MHC-Router	10.0.0.100	255.255.0.0	N/A	172.0.0.1	10.0.0.1
				172.0.0.100	255.255.255.0.	N/A	172.0.0.1	10.0.0.1

enjoy,