Sites n Servers Team Blog

Save unnecessary Business expenses. Go Green!

2010-05-03T23:51:00.001-07:00

We now offer IT Consultancy Services to help companies Save Unnecessary Expenses and also help them save Environment. Check out our presentation

Save unnecessary Business expenses. Go Green!

View more presentations from Sites n Servers.

Configuration Manager Documentation Library Update for February 2010

2010-03-01T23:39:00.000-08:00

Configuration Manager Documentation Library Update for February 2010

The Configuration Manager documentation library (http://technet.microsoft.com/en-us/library/bb680651.aspx) has been updated on the Web and the latest content on the Web has Updated: February 1, 2010 at the top of the topic.

What's New in the Configuration Manager Documentation Library for February 2010
The following information lists the topics that contain significant changes since the January 2010 update.
Supported Operating Systems and Hard Disk Configurations for Operating System Deployment

- Updated to clarify that Windows 7 and Windows Server 2008 R2 are supported by operating system deployment in Configuration Manager 2007 SP2.
Operating System Deployment Task Sequence Variables

- Updated to add the _SMSTSTimezone task sequence variable.
Apply Network Settings Task Sequence Action Variables

- Updated to correct the name of the OSDDNSSuffixSearchOrder task sequence variable.
Log Files for Operating System Deployment

- Updated to correct the location of the CreateTSMedia.log file.
How to Verify That Site Information Is Published to Active Directory Domain Services

- Updated to clarify that Configuration Manager 2007 does not use the msSMSSiteBoundaries attribute for the site code object.
Program Properties Page and Program Name Properties: Environment Tab

- Updated with corrected information that Allow users to interact with this program is available only when Program can run is configured for Only when a user is logged on or Whether or not a user is logged on.
Configuration Manager in Multiple Active Directory Forests

- Updated to clarify that to discover a computer resource in another forest by using Active Directory System Discovery, there must be a forest trust between the site server forest and the forest where the computer is located. The absence of the trust is also added to Troubleshooting Discovery Issues and the troubleshooting entry "Discovery Does Not Return Any Results". For more troubleshooting information about this requirement, see The Configuration Manager Support Team Blog post: Configuration Manager AD system discovery will not work across external trusts starting with Service Pack 2.

SOURCE: http://blogs.technet.com/configmgrteam/archive/2010/02/25/announcement-configuration-manager-documentation-library-update-for-february-2010.aspx

Why SharePoint

2009-12-25T05:40:00.001-08:00

Check out this SlideShare Presentation:

Why SharePoint

View more presentations from Sites n Servers.

How we use the power of SharePoint?

2009-12-12T01:50:00.001-08:00

How we use the power of SharePoint?

Issues that we used to face daily

We usually have several projects running at a time and multiple teams working on it. Somtimes, people prefer to work from Remote locations (home or Client's locations). We all know Sharing and Finding documents is the biggest hurdel when we are not in our office. There was no place for people working on Remote Locations who need to Track the progress being made on the Projects they are working on.

How SharePoint helped us

We use SharePoint to track our Projects using Gantt Charts. So SharePoint is also working as a Project Management Solution for us :)

Now people can easily collborate and share the information about the Project with their Team mates or peers who are working on other projects.
Senior Managers can easily generate reports and track changes while sitting in the comfort of their cabins.
Our clients can also see the Progress being made on their Projects easily through an Extranet URL.

SharePoint works as a Document Management System for us.

We now store all our document on the SharePoint Document Libraries.
We can easily Search for the Document.
SharePoint helps us maintain integerity and consistency of the data being uploaded. It validates the data before uploading.
SharePoint helps us maintain previous versions of documents.
We now have a Retention Policy for documents.
We now use the Approval Workflow so that the document is published only when it is Approved.
Since all our documents are stored at a Centralized location, so now we can easily Backup our Data. Infact, we have scheduled the backup to happen automatically. So no more worries :)
Now we maintain just one copy of each Document. We don't have to email the documents to each other and choke our Exchange Server.
It helps us in keeping our Records Organized.

SharePoint is secure!

Our Data and Information is totally secured thanks to enhaced Security settings which allows us to secure an Item, List or or the Whole Site Collection. So now only Authorized person can view the data and information.
We can even hide the webparts from some users and show it to some other users based on our descrition.

We have converted all our Paper forms into Computerized forms. So now at the end of the month or year, we can easily create reports and ofcourse, we are helping the enviroment by saving TREES!
SharePoint works as a Communication Platform

Team mates usually subscribe for alerts or RSS. So now they get an email as soon as some changes or adds a document, an item to the list / document library. So now the Team mates have the latest information always available.
We post the latest Anouncements about the Company or Projects or upcoming Birthdays or Anniversaries on our Intranet Portal.
We have our internal Team Blog hosted on SharePoint where we all share our feelings, expriences or anything with the Team. Peopel can post ideas or information to blogs and wikis.
Use search and My Site to locate colleagues with specific expertise or knowledge.

How to prepare a hard drive for BitLocker Drive Encryption using the Format and Partition Disk Task in an SCCM 2007 OSD Task Sequence

2009-12-12T01:42:00.001-08:00

How to prepare a hard drive for BitLocker Drive Encryption using the Format and Partition Disk Task in an SCCM 2007 OSD Task Sequence

When using the "Enable BitLocker" in an SCCM 2007 OSD Task Sequence to deploy Windows Vista or Windows Server 2008, BitLocker Drive Encryption fails to be enabled. Opening the BitLocker Drive Encryption control panel shows the following error message:

The drive configuration is unsuitable for BitLocker Drive Encryption. To use BitLocker, please re-partition your drive according to the BitLocker requirements.

RESOLUTION

This problem happens because the "Format and Partition Disk" task (usually called "Parition Disk") is not correctly configured to partition the disk according to the BitLocker requirements. Bitlocker requires two partitions. The first partition is the boot partition and has to be at least 1.5 GB. The second partition is the partition to be encrypted and is where the OS is installed.

To use the "Format and Partition Disk" task (usually called "Partition Disk") to properly partition and format the hard drive for use with BitLocker Drive Encryption:

1. In the SCCM 2007 admin console, open and edit the Task Sequence that is deploying the Windows Vista or Windows Server 2008 OS and has the "Enable BitLocker" task

2. Click on the "Format and Partition Disk" task (usually called "Partition Disk")

3. Make sure that "Disk number:" is selected to the disk where BitLocker Drive Encryption is going to be used (usually 0) and that "Disk type:" is selected to "Standard(MBR)".

4. Delete any currently configured steps Under "Volume:"

5. Click on the yellow starburst to create a new step

6. In the "Partition properties" window:

a. Next to "Partition name:", enter the name that the user wants to give to the partition. If desired, this can be left blank.

b. Next to "Partition type:", select "Primary"

c. Under "Partition type:", select "Use specific size" and next to "Size:" enter 1500 and select "MB" in the drop down menu.

d. Click on the "Make this the boot partition" option

e. Under "Formatting options", next to "File system:", make sure that "NTFS" is selected in the drop down menu, and click on the "Quick format" option.

f. Under "Advanced options", next to "Variable:", enter in BootPartition

g. Click on the "OK" button

7. Click on the yellow starburst to create second step

8. In the "Partition properties" window:

a. Next to "Partition name:", enter the name that the user wants to give to the partition. If desired, this can be left blank.

b. Next to "Partition type:", select "Primary"

c. Under "Partition type:", select "Use a percentage of remaining free space", and then next to "Size(%):", enter 100.

d. The "Make this the boot partition" should be greyed out and cannot be selected. If it is not greyed out, check step 6d.

e. Under "Formatting options", next to "File system:", make sure that "NTFS" is selected in the drop down menu, and click on the "Quick format" option.

f. Under "Advanced options", next to "Variable:", enter in OSPartition

g. Click on the "OK" button

9. Click on the "Apply Operating System Image" task (usually called "Apply Operating System")

10. Next to "Destination:" under "Select the location where you want to apply this operating system.", select "Logical drive letter stored in a variable" from the drop down menu

11. Next to "Variable name:", enter in OSPartition

12. Click on the "OK" button to save the Task Sequence

The above steps will properly install the OS drive to C:.

If mutiple hard drives are involved, or if mutiple partitions are desired, the above steps will need to be modified according to the user's requirements.

If after the OS is deployed, the user wants to hide the BitLocker Boot Partition in Windows Vista or Windows Servr 2008, please follow KB231289:

KB231289 - Using Group Policy Objects to hide specified drives
http://support.microsoft.com/kb/231289

For more information on BitLocker Drive Encryption partition requirements, please see

Set up your hard disk for BitLocker Drive Encryption
http://windowshelp.microsoft.com/Windows/en-us/help/06dd6cf9-420c-4819-8eaf-f0e7c51300741033.mspx

KB933246 -Description of the BitLocker Drive Preparation Tool
http://support.microsoft.com/kb/933246

NOTE - It is not necessary to use the BitLocker Drive Preparation Tool described in KB933246 in the Task Sequence as long as the above steps are followed. KB933246 is being provided for informational purposes only.

Promoting Secondary Site running on Windows 2008 Server as RODC (Read Only Domain Controller)

2009-12-12T00:52:00.001-08:00

Promoting Secondary Site running on Windows 2008 Server as RODC (Read Only Domain Controller)

We understand that the installation of SCCM Site is supported on Windows 2008 RODC Server but we came up with a scenario where we wanted the existing Secondary Sites to be promoted to RODC.

As per Technet: http://technet.microsoft.com/en-us/library/cc431377.aspx:

Installing Configuration Manager 2007 SP1 primary and secondary site systems is supported on Windows Server 2008 read-only domain controller (RODC) computers. During site installation using the Configuration Manager 2007 Setup Wizard, the wizard will identify that the site is being installed on an RODC and search for a writable domain controller to create the necessary groups required by the type of
site installation. However, when installing secondary sites using the Install Secondary Site Installation Wizard from a Configuration Manager console, the groups required for the secondary site installation must be pre-created in Active Directory Domain Services before beginning the installation.

RESOLUTION
The Objective that we had in our minds: To see if promoting the existing Secondary Site Server to RODC will allow the secondary Site to function properly.

This was the Result:

By following the below steps we confirmed that the site works fine with the configured roles (Roles used to confirm are Proxy MP and DP). Since these are the major roles and if they work other roles should also work fine.

We followed the below steps:
1.            Installed fresh Windows 2008 Enterprise (Computer name 2008SecSite)
2.            Installed SCCM Secondary Site on the server (Site Code: NEW)
3.            Configured the site to be a Distribution Point and Proxy Management Point
4.            Confirmed the site is working fine by checking MPcontrol.log, Distmgr.log, Despool.log, Sender.log and MP_GetAuth.log.
5.            Before running DCPROMO to promote the server to RODC created the following two groups manually on the Writeable Domain Controller

a) SMS_SiteSystemToSiteServerConnection_SEC. (Domain Local - Security)

b) SMS_SiteToSiteConnection_SEC (Domain Local - Security)

c) Added the Primary Site server computer account to the group
SMS_SiteSystemToSiteServerConnection_SEC

Find more about these groups here:

About the Site System to Site Server Connection Group
http://technet.microsoft.com/en-us/library/bb680864.aspx
About the Site to Site Connection Group

http://technet.microsoft.com/en-us/library/bb632850.aspx

Make sure both the groups have Read and Change permission on default share
SMS_SiteCode on the secondary site

Manage Computers in different AD forest

2009-12-06T02:36:00.000-08:00

I was working on a case few days back and a question popped in my mind: What all do I NEED Manage Computers in different AD forest

I researched and found answers to most of the requirements in Technet. Heres what all you would need to Manage Computers in a different AD Forest

To manage a client where no trusts exist between the client and site:
• You don’t need to discover the client to install it, assign it to a site, and manage it. Client discovery is a requirement for Client Push installation but there are other methods to install clients that might be more suitable for this scenario. More information: Determine the Configuration Manager Client Installation Method to Use

• You don’t need WINS, but you do need name resolution between the two forests – DNS forwarding for example. More information: Configuration Manager and Name Resolution

• You do need a server locator point to complete site assignment for these clients. The only exception is when the client is assigned to an Internet-based site. More information: Configuration Manager and Service Location (Site Information and Management Points)

• You don’t need to publish the server locator point in WINS – assign it to the client during installation. More information: How to Specify the Server Locator Point for Configuration Manager Client Computers

• I recommend that you manually install the client and specify the site code and server locator point (recommended because this client installation method has the least number of dependencies). More information: How to Install Configuration Manager Clients Manually

• You do need a Network Access Account. More information: How to Configure the Network Access Account

WSUS: How to move SUSDB from one SQL 2005 server to another SQL 2005 server

2009-12-01T03:10:00.000-08:00

Lot of times, we come across the same situation, where in we have to move the SUSDB to another server. I did the same last weekend and here's how I did it.

Environment:
WSUS 3.0 SP1 runing on Win 2003 SP2 STD x86
SUSDB hosted by remote SQL 2005 STD x86 server

Solution:
1) Right-click IIS Admin Service, and then click Stop.

2) Right-click Update Services, and then click Stop.

3) On the old SQL server, DETACH the SUSDB database.

4) Copy the database files (MDF and LDF) from the old SQL server to the new SQL server. (Make a backup copy of these files as well.)

5) Attach the database files as SUSDB to the new SQL server.

a. Verify permissions on the SQL Server instance. In SQL Server Management Studio, open the instance and select Security, then Logins. The NT AUTHORITY\NETWORK SERVICE account should be listed as a login. If not listed, add the account as a login.

b. Verify permissions on the database. Right-click the database, select Properties and then click Permissions. The NT AUTHORITY\NETWORK SERVICE account should be listed as a login. If not listed, add the account as a login.

c. Verify members of the webService role. Under the WSUS database, select Roles, then right-click webService and select Properties. The NT AUTHORITY\NETWORK SERVICE account should be listed as a member of this role. If it is not, it should be added.

6) Back on the WSUS server, open the registry editor: Click Start, click Run, type regedit, and then click OK.

7) Browse to HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, and in the Value box, type [ServerName]\[InstanceName],and then click OK. If the instance name is the default instance, then simply type [ServerName].

8) Click Start, point to Programs, point to Administrative Tools, and then click Services.

9) Right-click IIS Admin Service, and then click Start.

10) Right-click Update Services, and then click Start.

I hope this helps all of you guys :)

Admin console crashes with "MMC has detected an error in a snap-in and will unload it"

2009-11-21T00:41:00.000-08:00

Admin console crashes with "MMC has detected an error in a snap-in and will unload it"

ISSUE

>> Issue with SCCM SP1 Admin console
>> Opening Site Status node takes 1 minute
>> Site starts loading 25 sites each time
>> Waits for some time and loads another 25 sites and finally the console crashes with "MMC has detected an error in a snap-in and will unload it"

SmsAdminUI.log
"Transport error; failed to connect, message: 'The ConfigMgr Provider reported an error."
More recent errors were all pointing to SQL connectivity - "SQLMessage = "[01000][768][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (SECDoClientHandshake())."

RESOLUTION
Increase the default 128MB WMI provider memory quota to 512 MB by stepping through the following:
- Open WBEMTest and connect to root
- Click Open Instance and enter: __ProviderHostQuotaConfiguration=@
- Double click the MemoryPerHost property, change the value to 402653184 and click Save Property
- Double click the HandlesPerHost property, change the value to 8192 and click Save Property
- Finally, click Save Object, close all WBEMTest windows
- Reboot the server or restart the WMI service

Initially we tried increasing the size to 384 MB which didn't resolve the issue fully. Modifying the Value to 512 MB resolved the issue.

We don't want to increase this value too high but high enough to let it work.

Distribution Point (DP) error: "doesn't have enough free disk space"

2009-11-21T00:31:00.001-08:00

Distribution Point (DP) error: "doesn't have enough free disk space"

I was sending out a package yesterday which was about 1.2GB in size. I started facing issues with the Distribution Point. It was not being updated.

On checking the Distmgr.log, I came to know that there was an error: “doesn't have enough free disk space”. Even though I could see space in the drive (~1.4GB), but still it said that it doesn’t have enough free disk space.

The server needs disk space double the package size as the Distribution Points receives .PCK file, which gets decompressed on the Distribution Point. So we need space twice the package size.

After making more than 2.5 GB available space, the package got copied successfully.

How to rename the SCCM Database

2009-11-20T23:14:00.000-08:00

Hey guys lot of times, I hear my clients asking me if there is any way they can rename the ConfigMgr Database. I got some time this weekend, and finally was able to find out a way.

Here’s how I did it.

ConfigMgr 2007: How to rename the SCCM Database

We can change the Site Database name by running Site Reset Wizard.

Before running the Wizard make sure you have renamed the Database in SQL to custom name.

Follow the steps mentioned in below link to rename SQL DB

http://technet.microsoft.com/en-us/library/ms345378.aspx

--> While running Site reset, I selected "Modify SQL Server Configuration"

--> Under ConfigMgr Site database option gave the new name.

--> After completing the wizard everything was working fine except the Display name and some warning messages.

--> The name under "ConfigMgr site database server" site system role was still pointing to old DB name.

--> And I saw the below warnings:
“Microsoft SQL Server reported SQL message 911, severity 16: [08004][911][Microsoft][ODBC SQL Server Driver][SQL Server]Could not locate entry in sysdatabases for database 'SMS_NEW'. No entry found with that name. Make sure that the name is entered correctly.”

--> To resolve both the issues I made changes manually to the SiteCtrl file.

I followed the below steps to make the changes.

1. Stop the SMS_Executive and SMS_Site_Component_Manager services on the Site Server.

2. Backup the SiteCtrl.Ct0 file from the folder %Program Files%\Microsoft Configuration Manager\Inboxes\SiteCtrl

3. Open the SiteCtrl.Ct0 file in notepad update the following section. In the example below SMS_SNS is my default database name. Modify the database name to reflect the new name.

BEGIN_SYSTEM_RESOURCE_USE
RESOURCE
Server><["Display=\\SCCMSRV2\"]MSWNET:["SMS_SITE=SNS"]\\SCCMSRV2\ >
ROLE
BEGIN_PROPERTY_LIST

(Change SMS_SNS to new DB name)
END_PROPERTY_LIST
END_SYSTEM_RESOURCE_USE

4. Save the file and restart the Services.

With the above changes I was able to resolve the warnings and correct the display name.

Note: Apart from this I noticed Reporting Point, Reporting Services Point and Custom Maintenance task are few of the things need re-configuration. Basically any component which uses static database entry while connecting.

I am still monitoring the health of the database and the environment and its been quite a while now and I have not received any errors till now,

Hope this helps all of you. :)

FAQs for Branch Distribution Points

2009-11-09T02:06:00.000-08:00

I was going through some blogs and came across this very good article about Branch Distribution Point. I think it answers lot of questions.

FAQs for Branch Distribution Points
http://blogs.technet.com/wemd_ua_-_sms_writing_team/archive/2008/07/27/faqs-for-branch-distribution-points.aspx

How To Upgrade SMS 2003 to ConfigMgr

2009-11-04T03:17:00.000-08:00

I was researching on upgrading SMS 2003 environment to SCCM 2007 and came across a very good blog which has step by step information about everything that is required.

I will try to create an SMS 2003 environment during the weekends and then try to upgrade that to SCCM 2007 >> SCCM 2007 SP1 >> SCCM 2007 R2 >> SCCM 2007 SP2... let's see how it goes. I will keep you updated :)

How To Upgrade SMS 2003 to ConfigMgr
http://myitforum.com/cs2/blogs/socal/archive/2007/12/17/how-to-upgrade-sms-2003-to-configmgr.aspx

Software Updates Report

2009-11-04T03:15:00.000-08:00

Lot of times we hear people saying "What is the best report to check if it Software Updates are working or not?". I was just looking around and found a very interesting article which tells you what does each report mean and what data they fetch.

About Software Updates Reports

http://technet.microsoft.com/en-us/library/bb632839.aspx

Operating System Deployment Terminology

2009-10-31T02:10:00.000-07:00

The following terms are used when describing concepts and actions related to Microsoft System Center Configuration Manager 2007 operating system deployment.

Image

The image is a collection of files and folders that duplicates the original file and folder structure of an existing computer, including the file and folder structure of the operating system, or that is a file-based replica of a hard disk. An image often contains other files added by the Configuration Manager 2007 administrator. Operating System Deployment supports Windows Image format (WIM).

Target computer

The target computer is the computer on which you install a Microsoft® Windows operating system image using Configuration Manager 2007 Operating System Deployment.

Reference computer

A reference computer is a fully-configured computer from which you generate the WIM file that will be used to distribute operating system images to target computers.

Source Computer

The source computer is an existing computer that is managed by Configuration Manager 2007. The source computer contains the user state data and settings that will be migrated to a new destination computer. The source computer must have a computer association with the destination computer for side-by-side migration scenarios.

Destination Computer

The destination computer is the computer that will receive the user state data and settings that are migrated from a source computer. The destination computer must have a computer association with the source computer for side-by-side migration scenarios.

Sysprep

Sysprep is a Windows system preparation tool that facilitates image creation on reference computers running Windows operating systems, and the preparation of an image for deployment to multiple target computers. Sysprep generalizes the reference computer by removing all computer-specific information such as security identifiers, network addresses, and the computer name. When the generalized image is cloned to other computers, the other computers establish their own identity and don't duplicate the identity of the reference computer.

User State Migration Tool (USMT)

The User State Migration Tool (USMT) is a Windows utility used by administrators to collect a user's documents and settings, called the user state data, before an operating system deployment is performed, and then restores the user state data after the installation.

USMT migrates user files and settings during large deployments of Microsoft Windows 2000, Microsoft Windows XP or Microsoft Windows Vista operating systems. USMT captures desktop, network, and application settings as well as a user's files, and then migrates them to a new Windows installation in order to improve and simplify the migration process.

USMT 3.0 supports the capture of user settings (known as scan state) from computers running the Windows 2000 operating system or later, and the restore of user settings (known as load state) on computers running the Windows XP or Windows Vista operating systems.

USMT 2.61 supports the capture of user settings (known as scan state) from computers running the Windows 9x operating system or later, and the restore of user settings (known as load state) on computers running the Windows 2000 or later operating systems.

For more information about USMT see the Windows XP Professional Deployment Web page, see (http://go.microsoft.com/fwlink/?LinkID=88299). You can download USMT from the Microsoft Download Center, see (http://go.microsoft.com/fwlink/?LinkID=88300).

Windows Preinstallation Environment (Windows PE)

Windows PE 2.0 is a Windows operating system with limited services, built on the Windows Vista operating system platform. Windows PE is the boot image used by Operating System Deployment, and is used only in the preinstallation and deployment of Windows operating systems. Configuration Manager 2007 does not support earlier versions of Windows PE.

You can find detailed documentation about Windows PE, see (http://go.microsoft.com/fwlink/?LinkId=93917).

Windows Image Format file (WIM)

A WIM file represents the file format for an image captured using Operating System Deployment and is a compressed collection of files and folders.

Task sequence

A task sequence is a series of one or more task steps that can be advertised to Configuration Manager 2007 clients to run user-specified actions. Task sequences are used with Operating System Deployment to build source computers, capture an operating system image, migrate user and computer settings, and deploy an image to a collection of target computers. Task sequences can also be used to run other Configuration Manager 2007 actions, such as deploying Configuration Manager 2007 software packages or running custom command lines.

Task sequence step

A task sequence step is a component of a task sequence and represents a user-specified action that is run on a computer that the task sequence is advertised to. Task sequence steps always run entirely on the target computer, and never on a Configuration Manager 2007 site system.

Task sequence group

A task sequence group is a component of a task sequence and represents a collection of one or more task sequence steps.

How to identify your SQL Server version and edition

2009-10-31T01:57:00.001-07:00

Here is a concise list of SQL Server version numbers and the corresponding friendly name. If you need to know how to get the version number from you SQL server, check out the article below.

How to identify your SQL Server version and edition

http://support.microsoft.com/default.aspx/kb/321185

SQL Version	Version Number
SQL Server 2008 RTM	2007.100.1600.0
SQL Server 2008 SP1	2007.100.2531.0
SQL Server 2005 RTM	2005.90.1399
SQL Server 2005 SP1	2005.90.2047
SQL Server 2005 SP2	2005.90.3042
SQL Server 2005 SP3	2005.90.4035
SQL Server 2000 RTM	2000.80.194.0
SQL Server 2000 SP1	2000.80.384.0
SQL Server 2000 SP2	2000.80.534.0
SQL Server 2000 SP3	2000.80.760.0
SQL Server 2000 SP3a	2000.80.760.0
SQL Server 2000 SP4	2000.8.00.2039
SQL Server 7.0 RTM	7.00.623
SQL Server 7.0 SP1	7.00.699
SQL Server 7.0 SP2	7.00.842
SQL Server 7.0 SP3	7.00.961
SQL Server 7.0 SP4	7.00.1063
SQL Server 6.5 RTM	6.50.201
SQL Server 6.5 SP1	6.50.213
SQL Server 6.5 SP2	6.50.240
SQL Server 6.5 SP3	6.50.258
SQL Server 6.5 SP4	6.50.281
SQL Server 6.5 SP5	6.50.415
SQL Server 6.5 SP5a	6.50.416
SQL Server 6.5 SP5a Update	6.50.479

I hope this helps all of us!

Who we are? What We Do?

2009-10-31T01:25:00.000-07:00

We are experts in creating Technology Solutions for small & medium-sized business houses using latest Technologies like Microsoft Office SharePoint Server 2007 & Microsoft System Center Configuration Manager 2007

Sites n Servers works with the core belief that our success is measured by our ability to create value for clients. We works closely with you to develop the relationships and trust that allow us to help you take your business to the next level. Sites n Servers’ team is experienced, unbiased, hands-on and goal driven

Our goal is to provide you with excellent technology solutions and customer service. We continue to be dedicated first and foremost to meeting the needs of all of our clients, from the very beginning till the end. We look forward to helping you meet your technology needs in the year to come.

Our Offerings

1. Intranet Portal Development using Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0

2. Solutions using Microsoft System Center Configuration Manager 2007.

3. Infrastructure to deploy updates across the network using Windows Server Update Service 3.0

4. Domain Setup

Sites n Servers Team Blog

Save unnecessary Business expenses. Go Green!

Configuration Manager Documentation Library Update for February 2010

Why SharePoint

How we use the power of SharePoint?

How to prepare a hard drive for BitLocker Drive Encryption using the Format and Partition Disk Task in an SCCM 2007 OSD Task Sequence

Promoting Secondary Site running on Windows 2008 Server as RODC (Read Only Domain Controller)

Manage Computers in different AD forest

WSUS: How to move SUSDB from one SQL 2005 server to another SQL 2005 server

Admin console crashes with "MMC has detected an error in a snap-in and will unload it"

Admin console crashes with "MMC has detected an error in a snap-in and will unload it"

Distribution Point (DP) error: "doesn't have enough free disk space"

How to rename the SCCM Database

FAQs for Branch Distribution Points

FAQs for Branch Distribution Pointshttp://blogs.technet.com/wemd_ua_-_sms_writing_team/archive/2008/07/27/faqs-for-branch-distribution-points.aspx

FAQs for Branch Distribution Points

http://blogs.technet.com/wemd_ua_-_sms_writing_team/archive/2008/07/27/faqs-for-branch-distribution-points.aspx

How To Upgrade SMS 2003 to ConfigMgr

Software Updates Report

Operating System Deployment Terminology

How to identify your SQL Server version and edition

How to identify your SQL Server version and edition

Who we are? What We Do?

FAQs for Branch Distribution Points
http://blogs.technet.com/wemd_ua_-_sms_writing_team/archive/2008/07/27/faqs-for-branch-distribution-points.aspx