The Microsoft Assessment and Planning (MAP) Toolkit : MAP

The Microsoft Assessment and Planning (MAP) Toolkit is an agentless toolkit that finds computers on a network and performs a detailed inventory of the computers using Windows Management Instrumentation (WMI) and the Remote Registry Service. The data and analysis provided by this toolkit can significantly simplify the planning process for migrating to Windows® 7, Windows Vista®, Microsoft Office 2007, Windows Server® 2008 R2, Windows Server 2008, Hyper-V, Microsoft Application Virtualization, Microsoft SQL Server 2008, and Forefront® Client Security and Network Access Protection. Assessments for Windows Server 2008 R2, Windows Server 2008, Windows 7, and Windows Vista include device driver availability as well as recommendations for hardware upgrades.

 

System Requirements

• Supported Operating Systems: Windows 7; Windows Server 2003; Windows Server 2003 R2 (32-Bit x86); Windows Server 2003 R2 Datacenter Edition (32-Bit x86); Windows Server 2003 R2 Datacenter x64 Edition; Windows Server 2003 R2 Enterprise Edition (32-Bit x86); Windows Server 2003 R2 Enterprise x64 Edition; Windows Server 2003 R2 Standard Edition (32-bit x86); Windows Server 2003 R2 Standard x64 Edition ; Windows Server 2003 R2 x64 editions; Windows Server 2003 Service Pack 1; Windows Server 2003 Service Pack 1 for Itanium-based Systems; Windows Server 2003 Service Pack 2; Windows Server 2003 Service Pack 2 for Itanium-based Systems; Windows Server 2003 Service Pack 2 x64 Edition; Windows Server 2003 x64 editions; Windows Server 2003, Datacenter Edition (32-bit x86); Windows Server 2003, Datacenter Edition for 64-Bit Itanium-Based Systems; Windows Server 2003, Datacenter x64 Edition; Windows Server 2003, Enterprise Edition (32-bit x86); Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Enterprise x64 Edition; Windows Server 2003, Standard Edition (32-bit x86); Windows Server 2003, Standard x64 Edition; Windows Server 2008; Windows Vista; Windows Vista 64-bit Editions Service Pack 1; Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Enterprise; Windows Vista Enterprise 64-bit edition; Windows Vista Service Pack 1; Windows Vista Service Pack 2; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition; Windows XP; Windows XP 64-bit; Windows XP Professional 64-Bit Edition (Itanium) ; Windows XP Professional 64-Bit Edition (Itanium) 2003; Windows XP Professional Edition ; Windows XP Professional x64 Edition ; Windows XP Service Pack 1; Windows XP Service Pack 2; Windows XP Service Pack 3

• Hardware Requirements:
  • 1.6 GHz or faster processor minimum (dual-core 1.5 GHz or faster recommended for Windows Vista, Windows 7 or later, or Windows Server 2008 or later)
  • 1.5 GB of RAM minimum (2.0 GB of RAM recommended for Windows Vista, Windows 7 or later, or Windows Server 2008 or later)
  • 1 GB of available hard-disk space
  • Network adapter card
  • Graphics adapter that supports 1024x768 or higher resolution
• Software Requirements:
  • .NET Framework 3.5 SP1
  • Windows Installer 4.5
  • Microsoft Office Word 2007 or Word 2003 SP2
  • MIcrosoft Office Excel 2007 or Excel 2003 SP2
  • Microsoft Office Primary Interop Assemblies
  • Installation of all updates for the operating system and Microsoft Office
  • SQL Server 2008 Express Edition, SQL Server 2008, or SQL Server 2005

Note MAP supports x86 and x64 versions of operating systems.

Download Location

http://download.microsoft.com/download/4/6/F/46F45C42-D679-404E-9812-6053DD59A0D2/Microsoft_Assessment_and_Planning_Toolkit_Setup.exe

SQL Server 2008 Express Edition Limitations

SQL Server 2008 Express Edition is a fantastic option for those seeking the power of a full-featured relational database but with low performance requirements. It replaces the Microsoft Data Engine (MSDE) as the free version of SQL Server for application development and lightweight use. It remains free and retains the limitations of MSDE with respect to client connections and performance. It’s a great tool for developing and testing applications and extremely small implementations, but that’s about as far as you can run with it.

SQL Server 2008 Express has the following features and limitations:

• Limited to one CPU
• Limited to 1GB of RAM
• Database size limited to 4GB
• Does not offer database mirroring
• Does not offer log shipping
• Does not allow merge publication
• Does not offer Oracle replication
• Does not provide the Database Tuning Advisor, SQL Agent or SQL Profiler
• Does not offer SQL Server Analysis Services or Advanced Analytics

If you’re able to live within those limitations, SQL Server 2008 Express may be the best choice for you. It’s available for free download from the Microsoft website.
Another option for database developers is SQL Server 2008 Developer Edition. Unlike Express Edition, Developer Edition has no limitations on database size, performance characteristics or functionality. However, it’s only licensed for use by a single developer in a non-production development environment. Translated: you may use it for your own use in developing applications, but you may not allow others to access either the database or those applications. Before you put the applications into production, you must transfer the database to a fully licensed version of SQL Server.

You want to stop unwanted things while loading or want to get control of boot load files??

Ohh.. my systems dead slow after joins here… they given me T61 with 1 GB..  Where my system taking more than 1 Gb almost every time I am working my Page file…. 

I checked this utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and shows you the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You can configure Autoruns to show other locations, including Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond the MSConfig utility bundled with Windows Me and XP.

Autoruns' Hide Signed Microsoft Entries option helps you to zoom in on third-party auto-starting images that have been added to your system and it has support for looking at the auto-starting images configured for other accounts configured on a system. Also included in the download package is a command-line equivalent that can output in CSV format, Autorunsc.

You'll probably be surprised at how many executables are launched automatically!

 

Here is the link to download http://live.sysinternals.com/autoruns.exe

WINDOWS 2008 R2 : MY FINDINGS

 

There are 17 possible roles and 42 different features that can be enabled on Windows Server 2008 R2 Enterprise Edition.

Hyper-V role is not available for Windows Server 2008 R2 Itanium, Windows Server 2008 R2 Web, or Windows Server 2008 R2 Foundation.

Another problem in Windows Server 2008 Hyper-V was the inability to dynamically change the storage on a running VM. Unlike in the physical world where you can easily add or remove Universal Serial Bus (USB), eSATA, or iSCSI drives without shutting down a server, the only way to add or remove VHDs from a VM was to shut the VM down

SCCM client version

 SCCM client version

' RTM 4.00.5931.0001
' SP1 4.00.6221.1000
' SP2 4.00.6487.2000

Memory Limits in Windows OS

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows.

Memory type	Limit in 32-bit Windows	Limit in 64-bit Windows
User-mode virtual address space for each 32-bit process	2 GB Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT	2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit process	Not applicable	With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): x64:  8 TB Intel IPF:  7 TB 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space	2 GB From 1 GB to a maximum of 2 GB with 4GT	8 TB
Paged pool	Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value. Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value. Windows Home Server and Windows Server 2003:  530 MB Windows XP:  490 MB Windows 2000:  350 MB	128 GB Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM. Windows 2000:  Not applicable
Nonpaged pool	Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory. Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value. Windows Home Server, Windows Server 2003, and Windows XP/2000:  256 MB, or 128 MB with 4GT.	75% of RAM up to a maximum of 128 GB Windows Vista:  40% of RAM up to a maximum of 128 GB. Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM. Windows 2000:  Not applicable
System cache virtual address space (physical size limited only by physical memory)	Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value. Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value. Windows Home Server, Windows Server 2003, and Windows XP/2000:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.	Always 1 TB regardless of physical RAM Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM. Windows 2000:  Not applicable

 

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows 7 Ultimate	4 GB	192 GB
Windows 7 Enterprise	4 GB	192 GB
Windows 7 Professional	4 GB	192 GB
Windows 7 Home Premium	4 GB	16 GB
Windows 7 Home Basic	4 GB	8 GB
Windows 7 Starter	2 GB	2 GB

 

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version	Limit in 64-bit Windows
Windows Server 2008 R2 Datacenter	2 TB
Windows Server 2008 R2 Enterprise	2 TB
Windows Server 2008 R2 for Itanium-Based Systems	2 TB
Windows Server 2008 R2 Foundation	8 GB
Windows Server 2008 R2 Standard	32 GB
Windows HPC Server 2008 R2	128 GB
Windows Web Server 2008 R2	32 GB

 

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2008 Datacenter	64 GB	2 TB
Windows Server 2008 Enterprise	64 GB	2 TB
Windows Server 2008 HPC Edition	Not applicable	128 GB
Windows Server 2008 Standard	4 GB	32 GB
Windows Server 2008 for Itanium-Based Systems	Not applicable	2 TB
Windows Small Business Server 2008	4 GB	32 GB
Windows Web Server 2008	4 GB	32 GB

 

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows Vista Ultimate	4 GB	128 GB
Windows Vista Enterprise	4 GB	128 GB
Windows Vista Business	4 GB	128 GB
Windows Vista Home Premium	4 GB	16 GB
Windows Vista Home Basic	4 GB	8 GB
Windows Vista Starter	1 GB	Not applicable

 

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition	128 GB 64 GB with 4GT	2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition	64 GB	2 TB
Windows Storage Server 2003, Enterprise Edition	8 GB	Not applicable
Windows Storage Server 2003	4 GB	Not applicable
Windows Server 2003 R2 Datacenter Edition Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition	128 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Enterprise Edition Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition	64 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Standard Edition Windows Server 2003, Standard Edition SP1 Windows Server 2003, Standard Edition SP2	4 GB	32 GB
Windows Server 2003, Datacenter Edition	128 GB 16 GB with 4GT	512 GB
Windows Server 2003, Enterprise Edition	32 GB 16 GB with 4GT	64 GB
Windows Server 2003, Standard Edition	4 GB	16 GB
Windows Server 2003, Web Edition	2 GB	Not applicable
Windows Small Business Server 2003	4 GB	Not applicable
Windows Compute Cluster Server 2003	Not applicable	32 GB

 

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows XP	4 GB	128 GB
Windows XP Starter Edition	512 MB	Not applicable

 

Physical Memory Limits: Windows 2000

The following table specifies the limits on physical memory for Windows 2000.

Version	Limit in 32-bit Windows
Windows 2000 Professional	4 GB
Windows 2000 Server	4 GB
Windows 2000 Advanced Server	8 GB
Windows 2000 Datacenter Server	32 GB

 

Thanks to Ajay for recollecting this – Virus Clean with the help of Super DAT File

How to scan for viruses in DOS

 

Step 1 - Download and Extract the current SuperDAT Files

1. Click on the following link or type the URL into an Internet browser address bar:
   http://www.mcafee.com/apps/downloads/security_updates/superdat.asp?region=us&segment=enterprise
2. Click the I Agree button (if needed) to verify you have a current support agreement with McAfee.
3. English users, please click the link named sdatxxxx.exe (where 'xxxx' replaces the current SDAT version number) and save the file to your C:\ Drive.
4. All others please select the appropriate localized language from the drop-down list, click the link named sdatxxxx.exe (where 'xxxx' replaces the current SDAT version number) and save it to your C:\ Drive.
5. From the Taskbar, select Start and then Run.
6. In the Open field, type command and click OK. A DOS command window will open.
7. Type CD\ and press Enter. You should now be at a C:\ prompt.
8. Type SDATXXXX.EXE /E C:\SDAT and press Enter. (Note: The 'x's should be replaced with the appropriate numbers of the file that was downloaded above.) This will create an SDAT folder on the C:\ drive, and extract the SDAT files to this folder.
   Note: Windows XP Users with Service Pack 2 installed will be presented with a security warning when attempting to extract the file. Please click Run to continue the extraction process.
   
9. Once the C:\ prompt is displayed again, please type exit and press Enter.

Step 2 - Disable Windows System Restore

Windows XP utilize a restore utility that backs up and protects selected files automatically to the C:\_Restore folder. This means that an infected file could be stored there as a backup and VirusScan would be unable to delete these files. The System Restore utility must be disabled to remove any infected files from the C:\_Restore folder.

 

Windows XP

1. Right-click the My Computer icon on the Desktop and click Properties.
2. Click on the System Restore tab.
3. Put a check mark in the box next to Turn off System Restore.
4. Click the OK button.
5. You may be prompted to restart the computer. Click Yes to restart.
   Note: To re-enable the System Restore utility, repeat the steps above and in step 3 remove the check mark from the box next to Turn off System Restore.

Step 3 - Boot the Computer to DOS

1. If the computer is on: From the Taskbar, click Start, then Shutdown and choose Restart.
2. If the computer is off, turn the computer on.
3. When the opening splash screen appears, begin tapping the F8 key every second.
   Note: On some computers, if you press F8 too soon you will get a keyboard error. If this happens, press the F1 key to continue.
4. The Windows 2000 (or XP) Advanced Options Menu will appear. Use the arrow keys to choose Safe Mode with Command Prompt.
5. Login to your computer (if necessary).
6. When the computer is finished booting, the c:\> prompt will appear on the screen.
   Note: If there is anything typed after c:\>, type cd\ and press Enter.
7. Continue with the scan instructions below.

Step 4 - Scan the Computer

1. At the c:\> prompt, type cd sdat and press Enter.

2. Type scan.exe /adl /clean /all /sub /program /unzip /analyze /rptall /report report.txt and press Enter.

This will perform a virus scan, which will clean and delete any viruses you may have on your computer.

Explanation of DOS scan switches:

• /all - Scans all files
• /adl - Scans all local drives
• /sub - Scans within subdirectories
• /program - Enables Potentially Unwanted Program scanning
• /unzip - Enables archive scanning
• /analyze - Enables heuristics
• /clean - Sets the automatic action for the scanner to Clean anything detected
• /rptall - Enables verbose logging
• /report=C:\scan.txt - Saves the verbose logging as a text file in the root of C: called scan.txt

Multiple Infections

After the scan has run, a summary report of the scan will be created in the sdat folder on the C:\ drive. If this summary reports that your computer had multiple infections, it is recommended that you run the scan again to make sure the computer has been completely cleaned.
To determine if an additional scan is needed, please complete the following steps:

Step 5 - Review the Scan Report

1. Restart the computer into Normal Mode.
2. Double-click the My Computer icon.
3. Double-click the C:\ drive.
4. Double click the sdat folder.
5. Locate the file named report.txt and double-click to open.
6. The report contains several lines that look similar to this:
   
   If the top line named Possibly Infected has a number greater that 5, it is recommended that you run the scan in DOS again.
7. If you need to run the scan again, repeat the above instructions for Boot the Computer to DOS and Scan the Computer.

Additional Information

• How to perform a DOS virus scan in Windows Vista

Miscellaneous notes for “Dummy”s

Never select a PXE Distribution Point when deploying packages.

This may stop that PXE point from functioning. Use the list of DP Groups or select the specific DPs required.

When setting up Advertisements to execute at specific times use:-

UTC if you want the installation to start at the same time the world over regardless of local time. For example, if you want the installation to commence on all PCs regardless of location at 3:30AM Dallas time, select UTC on the Advertisement window.

Local Time if you want the installation to commence at a specific local time, ie at 2:00PM UK time and 2:00PM Canada time.

The “All Packages” canned report now shows all packages and not all packages at all distribution points.

If you wish to view all packages at a specific DP, please select the “All Packages for Distribution Point“ report.

Site WAN throttling

If a site with an SCCM DP Server has issues around bandwidth utilization and it seems that when SCCM deploys a new version of the Package (12GB) that users are impacted. The SCCM team can then throttle the SCCM utilization of the bandwidth during business Hours (6AM-6PM) so it only uses 50% or 20% of available bandwidth. Note that the less bandwidth the longer packages will take to reach the site.

Clean out obsolete client records

When a PC is being built from a PXE boot task sequence, an option exists for the immediate installation of other applications, This will only work if the flag is set on the packages program as per the below screen shot – “Allow the program to be installed from the Install Software Task Sequence without being advertised. If this flag is not set, the package will install approximately 2 hours after the task sequence is complete.

When the you notices packages without a source, they you can deleted those.

CREATE All Non Client Systems collection

 

The below is the query for creating All Non Client Systems:-

 

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 where SMS_R_System.Client = 0

Updates Performance Monitor counter : LODCTR

Updates Performance Monitor counter

 

LODCTR
    Updates Performance Monitor counter names and explain text for an extensible
counter

Usage:
    LODCTR [\\computername] filename
        computername is the name of the remote computer.
            Local machine is used if computername is not specified.
        filename is the name of the initialization file that contains
            the counter name definitions and explain text for an extensible
            counter DLL.

    LODCTR /S:<FileName>
        save current perf registry strings and info to <FileName>

    LODCTR /R:<FileName>
        restore perf registry strings and info using <FileName>

Note: any arguments with spaces in the names must be enclosed within
Double Quotation marks.

Seven Habits of Highly Effective People

1. HABIT ONE: BE PROACTIVE
2. HABIT TWO: BEGIN WITH THE END IN MIND
3. HABIT THREE: PUT FIRST THINGS FIRST
4. HABIT FOUR: THINK WIN – WIN
5. HABIT FIVE: SEEK FIRST TO UNDERSTAND THEN TO BE UNDERSTOOD
6. HABIT SIX – SYNERGISE
7. HABIT SEVEN: SHARPEN THE SAW

WMI Repair Command:- For Windows 2008 and Windows Vista/7

For For Windows 2008 and Windows Vista/7

winmgmt  /salvagerepository

 

For Windows Server 2003

rundll32 wbemupgd, RepairWMISetup

• cd /d %windir%\system32\wbem
• for %i in (*.dll) do RegSvr32 -s %i
• for %i in (*.exe) do %i /RegServer

Note that none of the above two methods restore the missing files related to Windows Management Instrumentation (WMI). So, below is a comprehensive repair procedure that restores all the missing WMI modules. In case of missing WMI modules, you may use the following method.

 

FOR XP

 

Comprehensive rebuild method

Important note:  If you've installed a Service Pack, you need to insert your Windows XP CD with Service Pack integration (called as the Slipstreamed Windows XP CD). If you don't have one, you may point to the %Windir%\ServicePackFiles\i386 folder for a recent version of the system files required during WMI repair. Or you may create a slipstreamed Windows XP CD and insert it when prompted.

Click Start, Run and type the following command, and press ENTER:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

Insert your Windows XP CD into the drive when prompted. Repair process should take few minutes to complete. Then restart Windows for the changes to take effect.

 

 

For XP/2k3/2000

//

1. Open a CMD prompt on the server and change directory to %windir%\System32\WBEM (\SysWOW64\WBEM on x64)

2. Execute the following:

FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
Net stop /y winmgmt
FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Net start winmgmt

Note: Don't attempt to compile the MOF files in the \bin\i386 folder on a site server, as we contain stub files (names start with an underscore character such as _smsprov.mof) that need to be populated with site specific data through other means.   

//

SCCM in Multi Forest design

Full information available for multiple forest is here
http://technet.microsoft.com/en-us/library/bb694003.aspx
http://technet.microsoft.com/en-us/library/bb694289.aspx

Top Rapidshare Search Engines

This summary is not available. Please click here to view the post.

Where Name0 in

Deleting Machines Directly From The SMS Database

To delete an individual machine from the SMS database using the SMS console it is necessary to create a collection using the direct membership rule wizard or base your new collection on a newly created Query. The first method is slow and can be time consuming, the second option just doubles your work and it the least desired method for most people.

The other automatic means in which you can remove or otherwise delete the machine(s) from the SMS database is to let the SMS_SQL_MONITOR service automatically remove the machine after it has reached its predefined Site maintenance task ‘Delete Aged Discovery Data’ and ‘Delete Aged Inventory History ‘ specifications if you have left it enabled. It is enabled by default and is set to 90 days. You can however change this to a more reasonable time period appropriate for your sites hierarchy if needed.

Below you will find a SQL query that will allow you to delete machines from the SMS database as the task “Delete Special” performs the removal process. It is important to note here that when you delete machines from a collection within the SMS console the machine is deleted from the database however the History table is not purged or removed. When you use the task Delete Special the machine is not only removed from the SMS database but the history for the machine is also deleted.

NOTE: You must uninstall the SMS client software to ensure that it does not report back in. If you are simply removing the machine name(s) from the SMS database because your site support staff has informed you that the machines were retired or re-imaged then this is not necessary. It is important to also note here that this is not a Microsoft supported means for deleting machines from the SMS database and should be used in a non production environment.

When you are done use the query in my earlier post entitled: ‘Searching Your SQL Database For A Specified Column String’ and search for the machine(s) that you just deleted to ensure that they have in fact been purged.

To delete multiple machines using the query that follows you can simply change the line that reads: Where Name0 = 'Machine_Name' To the following: Where Name0 in ('Machine_One', 'Machine_Two') as in the Deleting Multiple Machines SQL Query found at the end of this post.

• Deleting An Individual Machine SQL Query:

Insert DeletedMachines (SmsId)

Select IsNull(Sms_Unique_Identifier0,'')

From System_Disc

Where Name0 = 'Machine_Name'

And Sms_Unique_Identifier0 is not null

Delete System_Disc from System_Disc

Where Name0 = 'Machine_Name'

Delete System_Data from System_Data

Where Name0 = 'Machine_Name'

• Deleting Multiple Machines SQL Query:

Insert DeletedMachines (SmsId)

Select IsNull(Sms_Unique_Identifier0,'')

From System_Disc

Where Name0 in ('Machine_One', 'Machine_Two')

And Sms_Unique_Identifier0 is not null

Delete System_Disc from System_Disc

Where Name0 in ('Machine_One', 'Machine_Two')

Delete System_Data from System_Data

Where Name0 in ('Machine_One', 'Machine_Two')

Group Policy Software Deployment: Targeting the right computers with WMI filters

Group policy was introduced with Windows 2000, and is an easy way of centralizing many Windows settings. In addition to centralizing event log and firewall settings, I personally like the ability to deploy MSI-based software applications with Group Policy, since it makes it extremely easy to deploy new software packages.
Even though Software Installation only works only with MSI-based packages, it does make deploying MSI-based software packages extremely easy.  

We generally deploy software through Group Policy when three or more computers use it, since it's very easy to create a new package (if you already have a network share etc. setup, then you can literally do it in 2 minutes).

Before I list some of the useful WMI queries we use to target certain operating systems or computer types, there are a couple of things to note for those who are new to software deployment via group policy:

• Software packages are always installed right after a reboot, so they're mostly suitable for workstations.
• The network share which hosts the MSI files needs to give the computer accounts (e.g. DESKTOP1$) at least read access. Generally, giving EveryOne Read access works well unless you have a reason to restrict access to the software packages that you distribute.

Since the mechanism to distribute software is based on group policies, any sort of software package you create inside a group policy, will need to be assigned to an organizational unit (OU).
Since OUs can contain a large amount of computers that might not all need that particular software package, you can use two techniques to narrow down which computers receive the software:

1. Security Filtering
2. WMI Filtering

Security Filtering
With this method, you create a security group in Active Directory, place the computers that should get a particular software package into the group, and then specify this group in the Security Filtering list.
The screen shot below shows a group policy that will only be applied to members of the "Source Control Computers" group:

WMI Filtering
With this method, you can filter the computers which are affected by your policy, based on common properties of the Operating System. For example, some packages might distinguish between 32-bit and 64-bit, some packages might only work on Vista or later, whereas other packages apply only to servers. With WMI, you can target the right computers without having to mess with group memberships (though you will probably still need to do that). For example:

• 32-bit vs. 64-bit computers
• only workstations
• only computers running a certain OS
• only computers with a certain amount of RAM
• only computers of a certain brand

With WMI filtering, you just create the software group policy, for example:

• 7-Zip 32-bit
• 7-Zip 64-bit

and then apply the respective WMI filter to them. But lets cut to the chase, here are a few WMI queries that you can cut & paste:
Operating System 32-bit
Select * from Win32_Processor where AddressWidth = '32'
Operating System 64-bit
Select * from Win32_Processor where AddressWidth = '64'

Workstation
Select * from WIN32_OperatingSystem where ProductType=1
Domain Controller
Select * from WIN32_OperatingSystem where ProductType=2
Server
Select * from WIN32_OperatingSystem where ProductType=3
Some filters require multiple WMI queries, which are just chained together.
Workstation 32-bit
Select * from WIN32_OperatingSystem where ProductType=1
Select * from Win32_Processor where AddressWidth = '32'
Workstation 64-bit
Select * from WIN32_OperatingSystem where ProductType=1
Select * from Win32_Processor where AddressWidth = '64'

Windows XP
Select * from WIN32_OperatingSystem where Version='5.1.2600' and ProductType=1
Windows Vista
Select * from WIN32_OperatingSystem where Version='6.0.6002' and ProductType=1
Windows 7
Select * from WIN32_OperatingSystem where Version='6.1.7600' and ProductType=1
Windows 2003
Select * from WIN32_OperatingSystem where Version='5.2.3790' and ProductType>1
Windows 2008
Select * from WIN32_OperatingSystem where Version='6.0.6002' and ProductType>1
Windows 2008 R2
Select * from WIN32_OperatingSystem where Version='6.1.7600' and ProductType>1
WIN32_OperatingSystem of course includes more information that can be useful for WMI queries, such as a descriptive name of the installed OS ("Name") as well as the service pack installed ("ServicePackMajorVersion").
Manufacturer (e.g. DELL)
Select * from WIN32_ComputerSystem where Manufacturer = 'DELL'
Installed Memory (e.g. more than 1Gb)
Select * from WIN32_ComputerSystem where TotalPhysicalMemory >= 1073741824

For more information, check out these resources on WMI:
WMI
Secrets of Windows Management Instrumentation
Scriptomatic (Vista/Win2k8/Win7: run as administrator!)

Reset done by any user for Site Status (SMS_COMPONENT_STATUS_SUMMARIZER)

If any user done Site reset if found in red/yellow to set to OK… then below message will appear

 

also you will see below information in one of other message

“SMS Site Control Manager added a "Property List" item named "Reset SMS_COMPONENT_STATUS_SUMMARIZER:1269225968" to the actual site control file D:\apps\sccm\inboxes\sitectrl.box\sitectrl.ct0.

This addition occurred as a result of a site configuration change request in delta site control file D:\apps\sccm\inboxes\sitectrl.box\incoming\t1wv43np.CT1. The change will take effect in serial number 84 of the actual site control file.”

 

Hope this helps to find who has reset the SMS / SCCM Site

Remote Server Administration Tools RSAT

Remote Server Administration Tools(RSAT)

Download Location:-
http://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en

DirectAccess

VPN Reconnect

Offline Domain Join

BranchCache

New Group Policy capabilities

AppLocker

Domain Name System Security Extensions (DNSSEC)

Windows Deployment Services supports Windows 7 deployments

What is Disaster? DR?

An event, usually a major or catastrophic that denies access to the normal facility of business (or technology processing) for an extended period that would require relocation to an alternate site or sites.

Batteries recommended

SEMI - TUBULAR Batteries - These are Modified Versions of Automotive Batteries and are Designed for Inverter Applications .. They come with 18 Months Replacement Warranty + Some Rebate for the Next 6 months if battery Fails and Average Life of these Batteries is 3 years..These Batteries Need Topping of Distilled Water once in 3 4 Months .

Models  Recommended  by us :- EXIDE INVERTER + Series /  SF POWERBOX Series. ( 18 Months Replacement + next 6 Months 50% Rebate )

TUBULAR Batteries :-  These are the Batteries which are Specially Designed for Inverters , UPS & Telecom Purpose where Continuos Current is Required at the Time of Power Failure .. The Plates in the Batteries are Very Thick which gives you Excellent Power Back up and Life .. They Usually come with 2 Yrs & 3 Yrs Replacement Warranty and average Life of these Batteries is 5 -7 Years..there is no smell or fumes from these batteries and maintainance is required only once in 6-8 months

-------------------
Thanks,

Windows 7 Research deployment

　

Key Findings

• 46% are not waiting for the release of Service Pack 1 to deploy Windows 7

• 87% are planning to deploy Windows 7 compared to 47% who had plans to deploy Vista at a comparable point

after the operating system release

• 58% expect to deploy Windows 7 by the end of 2010

• 27% are using commercial tools for migration

• 57% are concerned about Windows 7, down from 67% in 2009

• 25% expressed concerns about performance, down from 47% in 2009

• 41% are anxious about stability, down from 62% in 2009

• 86% are concerned about software compatibility, consistent with 88% in 2009

-------------------
Thanks,

to know the user password last changed time Command

C:\>NET USER administrator | FIND /I "Password last set"
Password last set            2/17/2010 5:20 PM

C:\>

SMS_Outbox_Monitor and SMS_Inbox_Monitor Errors

 

When you see below kind of errors in your Site status…

 

 

 

 

Solution:- Connect to ConfigMgr Service Manager and connect to the problem Site and “Stop SMS_Inbox_monitor and SMS_Outbox_monitor and start it “

how to move the Site Database in Microsoft System Center Configuration Manager 2007 from a computer

INTRODUCTION
This article describes how to move the Site Database in Microsoft System Center Configuration Manager 2007 from a computer that is running Microsoft SQL Server 2005 to another drive on the same computer, or to another computer that is running SQL Server 2005.

MORE INFORMATION
In certain situations, you may have to move the Site Database from a computer that is running SQL Server 2005 to another drive, or to another computer that is running SQL Server 2005. For example, the following situations may require that you move the Site Database:

•You experience hardware issues on the server that you currently use. Additionally, you do not consider the server to be reliable.
•You have to move the Site Database and the log file to a different volume because the database requires more space, or because you want to improve performance.
•The server that you currently use is leased. The lease on the server is scheduled to expire soon.
•New hardware standards have been developed and approved. You must upgrade the computer that is running SQL Server 2005 to the new hardware specifications.
SQL Server 2005 supports the following:

•You can move files and log files from one computer to another computer if both computers are running SQL Server 2005.
•You can move data files and log files from one instance of SQL Server 2005 to another instance of SQL Server 2005 if both instances are on the same computer.
•You can move data files and log files from one volume to another volume on a computer that is running SQL Server 2005.
For more information about these functionalities in SQL Server 2005, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/library/ms203721.aspx

PREREQUISITES
Before you move the Site Database from a computer that is running SQL Server 2005 to another drive or another computer that is running SQL Server 2005, follow these steps:

1.Back up all the databases from their current locations. This includes the master database.
2.Verify that you have system administrator permissions on both the computers that are running SQL Server 2005.
3.Verify that you have configured the computer where you want to move the Site Database exactly like the computer that currently hosts the Site Database.
4.Verify that you know the name and the current location of the Site Database.
5.Stop the following Configuration Manager services on the Microsoft System Center Configuration Manager 2007 site server:
• SMS_EXECUTIVE Service
• SMS_SITE_COMPONENT_MANAGER Service
• SMS_SITE_SQL_BACKUP Service
• SMS_SITE_VSS_WRITER
Note: You can stop all of these services using the Preinst.exe utility by running the following command without the quotes:

"Preinst.exe /STOPSITE"

Preinst.exe is included with Microsoft System Center Configuration Manager 2007 Server and is located in the following path:

Drive:\Program Files\Microsoft Configuration Manager\bin\i386\00000409 (the last folder is dependent upon the language of the product, 00000409 is for the English version).

Note: If you are running the SMS Provider and the Site Database on the same SQL 2005 Server, and you are moving the Site Database to a new server, you will also need to modify the SMS Provider Configuration in order to move it as well, For more information about moving the SMS Provider in Microsoft System Center Configuration Manager 2007, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/library/bb693923.aspx.

MOVING THE DATABASE
To move the Site Database from a computer that is running SQL Server 2005 to another drive or another computer that is running SQL Server 2005, follow these steps:

Step 1: Detach the database
1. On the computer that currently hosts the Site Database, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2. Click the appropriate values in the Server type list, in the Server name list, and in the Authentication list. Then, click Connect.

3. Expand the Databases folder, right-click the SMS_ folder, point to Tasks, and then click Detach. Note that the Detach command is visible only if the following conditions are true:

• You are a member of the sysadmin fixed server role.
• The server to which you are connected is running SQL Server 2005.

4. Verify the status of the Site Database. Note that to successfully detach the Site Database, the status in the Databases to detach box in the Status column must read: "The database is ready to be detached." Optionally, you can update statistics before the detach operation. To do this, select the check box under the Update Statistics column in the Databases to detach box.

5. To close any existing connections in the Site Database, select the check box under the Drop Connections column in the Databases to detach box.

6. Click OK. The database node of the detached Site Database disappears from the Databases folder.

7. After the Site Database is detached, copy the SMS_.mdf file and the SMS_.ldf file to the drive and path you want to move it to, or to a folder on the computer to which you want to move the Site Database.

Note: The following path is the default path of the SMS_.mdf file:

Drive :\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

The following path is the default path of the SMS_.ldf file:

Drive :\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

Step 2: Attach the database

1. Click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2. Click the appropriate values in the Server type list, in the Server name list, and in the Authentication list. Then, click Connect.

3. Right-click the Databases folder, and then click Attach. Note The Attach command is visible only if the following conditions are true:

•You are a member of the sysadmin fixed server role.
•The server to which you are connected is running SQL Server 2005.
4. In the Attach Databases dialog box, click Add to specify the database that you want to attach.

5. Locate and then click the SMS_.mdf file. Then, click OK.

Note The following path is the default path of the SMS_.mdf file: Drive :\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

6. On the View menu, click Refresh to view the database node of the attached Site Database.

Note: If you moved the Site Database files to another drive on the same computer, then your move is complete, and you can start the following services:

•SMS_EXECUTIVE Service
•SMS_SITE_COMPONENT_MANAGER Service
•SMS_SITE_SQL_BACKUP Service
•SMS_SITE_VSS_WRITER
Step 3: Update the database server name

If you moved the Site Database to another server, you need to run the Microsoft System Center Configuration Manager Setup Wizard on the Microsoft System Center Configuration Manager 2007 Server to modify the SQL Server configuration to specify the new SQL Server name.

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

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

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

4. 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.

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

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

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

8. 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.

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

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

Note: If you also need to move the Software Update Services Database (SUSDB) you will need to stop IIS Admin Service, and Update Services Service and follow Steps 1 and 2 above to detach, then move the SUSDB.MDF and SUSDB.LDF files, then attach the SUSDB.MDF, in the new drive location or on the new SQL Server 2005.

Enjoy

High level of Tech Talk :- Take this Print

Communication errors between Site’s
SQL Server Errors

For Every Term you need to get a log file Name, Glossary should learn it

Site Server issues :-

1. Not able to connect to the Console
2. Site is not sending status messages, the procedure to confirm and the default report
3. Site Server Slow or CPU High Utilization
4. backlogs finding
5. Backlogs Story…
6. MY Script to check the Backlogs
7. Database errors related to Site Server and SQL
8. Importance of SMS Provider
9. Collections are not appearing in the hierarchy log file
10. Some of IMP Log Files
11. Status messages not for set to clear you must understand what happens when we set to clear and act to the situation
12. SMS 2003 Troubleshooting Workflow
13. News / MYITForum Group Importance
14. Backup of Sites
15. Uninstallation of Sites
16. Planning of Sites “”Configuration Manager Preplanning Worksheets””
17. Primary Site
18. Secondary Site
19. Just the DP
20. Boundaries
21. Boundary Overlapping
22. FSP and it’s history why we need FSP?
23. Site to Site key exchange
24. Possibility of NLBs and for MP and WSUS
    
25. OSD Coverage and steps
26. lets try MDT also
27. If possible Lets try Native Mode also

Client Issues:-

1. Client Installation Methods
2. Software Update point Based Client installation
3. Disadvantages of Client Push
4. Client installation Log files

Client Installation Troubleshooting:-

1. WMI Connectivity check
2. WMI Rebuild
3. WMI Log Files
4. MOF FILES RELATED TO WMI
5. Drive Space issues, FS.exe
6. Permissions, admin$, 64 bit ccm folder location & 32 bit control panel
7. Not found MP
8. not detecting the site code
9. client not assigning to site code and trying to install\
10. possible of command line option of ccmsetup.exe
11. ccmclean.exe
12. IMP log Files related to Client
13. patching related log file and issue
14. patching is failing to install
15. is sms/sccm client is manacle of things to automate?
16. Trace32.exe
17. Client Status Reports
18. SMS Client Health Monitor
19. Some of the “”State Messages in Configuration Manager 2007”

 

• MP Troubleshooting
• Reporting Point Troubleshooting
• Secondary Site Installation
• Ports Document
• patching the Systems
• Workstation Patching style and server patching status
• maintenance window
• SCCM R2 Advantages
• SCCM Features comparison with SMS

 

Inventory:-

Software inventory
Hardware inventory
SMS_def.mof File and tool from MYITFORM for registry key
mof compile
no idmif
idmif

 

 

Log files for Communication

1. Component Configuration Manager Troubleshooting
2. ADMINUI.log file
3. Delegation of Configuration / SMS Console
4. Status messages

Package Distribution Issues

1. Procedure to Confirm the Package  is reached to the DP And  Log File
2. Procedure to Package Source Version and Current Version finding
3. What is refresh and Update package and resend to DP?
4. How to Distribute the Packages to Multiple DPs? DP Groups?
5. IMP Log Files related to Distribution:- Sender and Scheduler and Distmgr.log
6. Compressed files like .Pck story
7. What is the Compressed Package?
8. What is Binary replication in Distribution?
9. What is the Package Creation Flow, I mean what kind of files gets changed in the work flow, like Dispooler and etc…
10. Importance of BITS on DP
11. Distribution points Related reports to the DP and Database Tables
12. Troublshooting steps for a Package is not reaching DP
13. Download package and run from DP
14. Virtual Applications and relationship with DP
15. In the Event of Distribution Point OS Failed how to proceed further to get it corrected?
16. Document from my blog DP in and Outs

Distribution Point Family and its Terms:-

 

1. Understanding of Advertisement?
2. Standard DP
3. Protected DP
4. Branch Distribution Point
5. peer DP
6. Nomad DP
7. Check in IE
8. More than 700 do we need another DP?
9. DFS and DP ?
10. File Server and DP ?
11. For each above Log files

Advertisement:-

1. Working style of Advertisement..
2. When we advertise the Command line Options that we can see…. for executing style
3. Default report that we can check for advertisement
4. Log files for advertisement
5. From console view of Advertisement status
6. If Advertisement failed how to make sure it to run again
7. Suppressing the Advertisement
8. how to use toolkit to see advertisement history
9. related information in control panel for advertisement
10. maintenance of Cache folder
11. If report is not showing more than 10000 rows for any advertisement
12. Advertisement to advertise Users and User groups
13. Advertisement interaction with user
14. Advertisement running with the administrator privileges and Logged in user account rights
15. Administrator Flow for Advertisement
16. advertisement to be appear in the add and remove programs

 

Other Topics

WOL in and Outs from my blog document

MP Issues

DP Issues

Preinst.exe

How to find the What deployment that are using… currentsly for this month

notification for Technet patching

PXE Issues and ports and fast port and iphelper

Wake on LAN ports and difference and unicast and subnet broad cast

Schema Extention two methods

Software Updates desgin and flow for how to create and deploy with the reports and log files

Small talk on OBT

SCCM Client Installation Batch Script

Psexec tool

psexplorer

Collections Database Table

Right Click Tools

System Center Clint Center

SCCM R3

Configuration Manager Preplanning Worksheets

Finally Glossary

IP Sec

Isolation of Domains

VLans

wdsutil

Multicasting

My Fav Photo

SQL 2005 Server Pre-Requisite Installation on 2008 server

SQL 2005 Server Pre-Requisite Installation

This document will outline the steps involved to prepare a SQL server for installation of SQL 2005 server. After these steps are done SQL 2005 Server with reporting services can then be installed.

References

How to install and how to configure SQL Server 2005 Reporting Services on a computer that is running Windows Server 2008

http://support.microsoft.com/kb/938245

You receive a warning message on the System Configuration Check page of the SQL Server 2005 Setup program on a computer that is running Windows Vista or a Server Core installation of Windows Server 2008

http://support.microsoft.com/kb/920201

Installation Steps

· Open Server Manager and choose click on the option "Roles" then choose " Add Roles".

· The Add Roles Wizard is displayed. Click "Next" to proceed past the "Before you[WH1] begin" wizard.

· In the "Select Server Roles box" select the option "Web Server (IIS)".

· The "Add features required for Web Server (IIS)?" dialog is displayed. Click the option that says "Add Required Features".

· The window will then return to the "Select Server Roles" dialog box with "Web Server (IIS)" selected.

· The "Web Server (IIS)" wizard is displayed, click "Next" to continue.

· The "Select Role Services" page is displayed.

· Here we need to make sure we have the correct items installed. (As various options are chosen on this dialog other options will be enabled as well).

· Under "Common HTTP Features" select "HTTP Redirection".

· Under "Application Development" select "ASP.NET".

· The "Add role services and features required for ASP.NET?" dialog should appear. Click "Add Required Role Services".

· The "Select Role Services" dialog will return to focus.

· Now select "ASP" under Application Development.

· Scroll down to the "Security" section and select "Windows Authentication".

· Scroll down the "IIS 6 Management Compatibility" section and select the following options:

IIS 6 Metabase Compatibility

IIS 6 WMI Compatibility

IIS 6 Scripting Tools

IIS 6 Management Console

· With the all the options plus the other defaults with that were enabled it should look like it does in screenshot below.

· Ensure the list looks like it does above and click "Next".

· The "Confirm Installation Selections" dialog is now displayed, click "Install" to begin the installation.

· When the installation has finished the "Installation Results" pages is displayed. Review this and make sure no errors or warnings are displayed.

· Click "Close" to return to "server Manager".

· The "Server Manager" window is then updated to reflect the "Web Server (IIS)" that was just installed.

· Choose "File - Exit" to return to the Windows desktop.

· At this point the pre-requisite components are installed and you are ready to begin the SQL 2005 installation.

---

[WH1]ok

Test from my Live

Test from my Live

Temporary Post Used For Theme Detection (f09a14fb-1a5a-477b-a681-136f8f77c996 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

This is a temporary post that was not deleted. Please delete this manually. (b2263d9e-ce89-4e5e-9405-0f00bd656100 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

IMP reports by me

Report Name: Clients that have not reported recently (Collection)

Category: SMS Site - Discovery and Inventory Information

Comment: This show report shows a list of clients that have not reported discovery data, hardware inventory, or software inventory in a specified number of days. An empty column indicates that a client has not reported any data of that type. A column with a '*' means that the client has reported data of that type within the specified time period.

　

Report Name: All active package distributions

Category: Software Distribution - Packages

Comment: This report shows all distributions points on which a package is currently being installed or removed

　

Report Name: Sites by hierarchy with time of last site status update

Category: SMS Site - General

Comment: Displays the list of sites in hierarchy order and shows the last time the site status was updated

-------------------
Thanks,

Example Scenarios for Configuration Manager 2007 used

1. Kim enables Active Directory Security Group Discovery. Every day, Configuration Manager 2007 queries Active Directory for all computers that are members of the Accounting security group.
   
2. Kim creates a query in the Configuration Manager 2007 console to find all members of the Accounting security group.
   
3. Kim creates a collection based on the query to find all members of the Accounting security group. If the Active Directory administrator adds a new computer to the Accounting security group, the next time Active Directory Security Group Discovery runs it will add the new computer to the Configuration Manager 2007 database. The next time the Accounting collection is evaluated, the query will find the new computer in the database and it will be added to the collection.
   
4. Kim enables the Advertised Programs Client Agent, so that all clients in his site will be able to receive software distribution packages.
   
5. Kim creates several distribution points in each site. If he configured only one per site, it might not be able to service all of the clients in that site.
   
6. Kim creates a package for the accounting application. He configures the package to read the source files from the CD and create a local copy of the package, because disks in his office sometimes disappear without his permission.
   
7. The application has a tool to create a customized Windows Installer file that will install the software with no user intervention and using all of the accounting department's preferred defaults. Kim creates one program to run the customized Windows Installer and he creates a second program to uninstall the accounting application, just in case. Both programs are configured to run whether or not a user is logged on, and both will run with administrative rights even if the logged on user is not currently an administrator, even if the client computer is running Windows Vista with User Access Control enabled.
   
8. The default package access accounts allow all users to read the package. Because only accounting members should have access, Kim removes the Users package access account and adds an account for the accounting group.
   
9. Kim copies the package to all distribution points in his site. He also copies the package to all distribution points in all child sites because there are some members of accounting in every site.
   
10. As soon as Kim completes the distribution point wizard, the site server immediately begins copying the files to the distribution points in his site. Kim purposefully waited until the end of the day to run the distribution point wizard so the network would be less busy. The sender controls the bandwidth utilization to the child sites, so it doesn't matter when Kim runs the distribution point wizard. The sender from the parent site copies the package to the child site in small chunks and verifies each chunk before sending the next one. After the entire package is successfully received at the child site, the child site server copies the package to all distribution points in that site.
    
11. After Kim has verified in the package status that the package has been distributed to all of his distribution points, he creates an advertisement. He configures the advertisement to use the accounting package and the program to run the customized Windows Installer file. He sets the advertisement to send the package and program to the accounting collection. He configures the advertisement to run next Wednesday at 4 pm in the client's time zone. He could have configured it to run at 4 pm UTC but some of the sites in other countries don't have local administrators and Kim doesn't want to get troubleshooting calls in the middle of the night if 4 pm in his site is midnight in a different site. Even though the application is rather large, Kim configures the advertisement to run even if the client computer is connected to a slow network boundary; this means that accounting users who work from home and connect using a VPN will still have to install the program. Kim makes a note to send out an e-mail to the home-based workers to let them know the large package is coming.
    
12. As soon as Kim completes the advertisement wizard, Configuration Manager 2007 creates a policy and sends it to the management points for all the sites. For the management points at the child sites, the sender at the parent site copies the policy to the site server at the child site and the child site server sends it to the site management point.
    
13. The clients in all the sites have been configured to poll for new policy every two hours because it provides a nice balance between getting software out quickly enough but not saturating the network with policy requests.
    
14. The next time a client in the Accounting collection polls the management point, it is told that it has software advertised to it. It asks for the location of the content and is given a list of distribution points in the site. The client sorts the list and finds three distribution points on the same subnet, so it picks one at random. The client connects to the selected distribution point and downloads the content into a local cache and then runs the program from the cache to install the accounting software.
    
15. After the software is installed, the client sends a status message indicating success.
    
16. Kim creates a report to show which clients have successfully installed the accounting software.
    
    
    --
    ----------------
    The One
    ----------------
    

P women

Here is the Some of the good food :--
Red carrot,beetroot,Prune's,pomegranate,spinach,Apple,Peanut Butter,Barley,Dried apricots,Dried blueberries,Prune Juice,
Dried Apricots,

by this you can avoid Hemoglobin issues:--

chicken liver,strawberries,grapefruit juice,broccoli,Dried fruits like apricots,prunes and raisins,lima beans,Black strap,molasses,pomegranate

IMP ons Wallnuts and barly and soya milk
-------------------
Thanks,

if you get the polcy agent log error...similar to below...

 

if you get the policy agent log error...similar to below...

Download of policy CCM_Policy_Policy4.PolicyID="{ddd31ca3-235d-4d47-b9b0-522ab79a4f18}",PolicySource="SMS:P04",PolicyVersion="1.00" failed (DTS Job ID: {2A03490A-B034-400B-87C4-08AC8AF07145}) PolicyAgent_PolicyDownload 3/2/2010 10:20:54 PM 3276 (0x0CCC)
Policy state for CCM_Policy_Policy4.PolicyID="{ddd31ca3-235d-4d47-b9b0-522ab79a4f18}",PolicySource="SMS:P04",PolicyVersion="1.00" was successfully reset. Policy download will be retried at next evaluation cycle. PolicyAgent_PolicyDownload 3/2/2010 10:20:54 PM 3276 (0x0CCC)
Download of policy CCM_Policy_Policy4.PolicyID="{E161A5A4-0DB4-40FD-8311-4BB2D50D03F5}",PolicySource="SMS:P04",PolicyVersion="14.00" failed (DTS Job ID: {BCB59159-EC2C-43B2-8BC7-2EE5BF5A4B72}) PolicyAgent_PolicyDownload 3/2/2010 10:20:54 PM 5684 (0x1634)
Policy state for CCM_Policy_Policy4.PolicyID="{E161A5A4-0DB4-40FD-8311-4BB2D50D03F5}",PolicySource="SMS:P04",PolicyVersion="14.00" was successfully reset. Policy download will be retried at next evaluation cycle. PolicyAgent_PolicyDownload 3/2/2010 10:20:54 PM 5684 (0x1634)
Download of policy CCM_Policy_Policy4.PolicyID="{E21A8331-0783-496F-ADD8-9ABCA051D707}",PolicySource="SMS:P04",PolicyVersion="1.00" failed (DTS Job ID: {145F36FE-C377-4FD8-960B-3B449AAD17A9}) PolicyAgent_PolicyDownload 3/2/2010 10:20:54 PM 3276 (0x0CCC)

 

You need to rebuild the WMI

--
----------------
Thanks
----------------

If you want to exclude some systems from CLIENT PUSH

If you want to exclude some servers from CLIENT PUSH
 

You can exclude the server from push installations by adding the server name to the registrykey ExcludeServers under HKEY_LOCAL_MACHINE/Software/Microsoft/SMS/Components/SMS_DISCOVERY_DATA_MANAGER on you site server. You find more information about this here:

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

 

wmi Rebuild from BLOG

//

1. Open a CMD prompt on the server and change directory to %windir%\System32\WBEM (\SysWOW64\WBEM on x64)

2. Execute the following:

FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s 
Net stop /y winmgmt 
FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s 
Net start winmgmt 

Note: Don't attempt to compile the MOF files in the \bin\i386 folder on a site server, as we contain stub files (names start with an underscore character such as _smsprov.mof) that need to be populated with site specific data through other means.   

//
-------------------
Thanks,

Client Troublshooting checks check list

Are you able to ping the server?
Is the server in Accepted list for supported servers?
Is Client Installed?
What is the Hartbeat status?
What is the S/W inventory Status?
What is the H/W Status?
Is this system is in active state in the Console?
Is the system has Dubplicate DDR records in Console?
What is the Incident Number you created for this server?
Are you able to login in to the server?
Do you have administrator rights on the server?
Is the Default Shares are enabled?
is free space more than 500Mb availabl on the server?
did you find the SMS agent Service in the Services.msc?
Is the SMS Agent Host Service is in started state?
are you able to connect to the WMI?
Did you intiated Machine Policy and H/w and S/w Polices ?
Is the Policy able to recive?
any errors in Inventoryagent.log?
Did you tried to restart the SMS Agent Host service?
any errors in ccmexec.log?
are you able to open the MP cert and MPlist URLs from the client system?
did the .xml file reached to MP?
What happend to mp_ddr log?
Did you find the server Name in dataldr.log and updated in the DB?
Remove the client system from the console and uninstall the client now delete the smscliconfig.file and log off and login now try to reinstall the client
-------------------
Thanks,

PXE Role Enable from Central ?

you can;t enable in the below hirarachy, you need to enable it from P01 only not from DC1

 DC1---Central Site
        |  
 P01--Primary Site
 |
 S01 Secondary Site

 

PXE ROLE Troubleshooting:

PXE ROLE Troubleshooting:

=========================

1.Uninstalled PXE Service Point Role
2.Uninstalled WDS
3.Deleted 'C:\RemoteInstall' folder or what ever the folder shared also check if any folder shared for PXE related
4.Rebooted then reinstalled WDS, rebooted
5.Reinstalled PXE Service Point Role
6.DHCP is not installed on this server and on the same subnet
7.Removed PSP/WDS again using the PXE.msi, same results
 
also can Try this:

1. Remove the SMS PXE role. Look at the PXESetup.log file to verify that the uninstall is complete and successful.

2. Uninstall the WDS server.

3. Reboot the machine.

4. Re-install the WDS server, but "do not configure it". Do nothing at all other than installing WDS.

5. Add the SMS PXE role. Look at the PXESetup.log file to verify that the installation is complete and successful.

6. Add the boot images to the SMS PXE DP share. Look at the distmgr.log file to verify that the replication of the boot image to the DP is complete and successful.

SCCM Vnext The Next version of SCCM 2007

The next release of Configuration Manager will focus on a few main areas:

• Improving client management experiences through enhanced, integrated software distribution models.  The next release of Configuration Manager will provide a framework for the right application format to be delivered to the user based on who they are, the device they are using, and their connection.
• Infrastructure improvements are also a main focus.  Optimizing site hierarchy, replication and content distribution on the backend.  For the managed client, improving client health and remediation capabilities will ensure that when a system is managed, it remains healthy and secure.  Part of this is also improving the Admin experience.  In the past we did this by reducing mouse clicks to get through an activity.  This is only part of the process.  Adding security models to enable role based administration, as well as improving the Admin console experience will ensure that Admins are more efficient everywhere.
• In addition, other areas of focus include expanding device management scenarios, model based configuration management and improving patch management services; just a few of the places we are focused on development.


Now available in beta for test.. Yep i wanted to do test in my LAB from next day

ConfigMgr07 R3

ConfigMgr07 R3

 

There're 3 main areas of enhancement being made to the core capabilities of ConfigMgr: Delta Active directory Discovery has 2 main tasks.

Discovering changes to users or machines that may effect targeting. Also, periodic full scans capture users and machines last logged time, ensuring active users or systems aren't made obsolete.
Fast Collections – When a Collection Membership Rule is configured to dynamically add new resources, a few things happen. This applies to a few resources.

Those that're initially discovered, OSD provisioned systems, HW inventories scanned systems, or ConfgMgr Client version upgrades. Admin Console Improvements helps Administrator save time in their daily tasks. For example, new right click options off a resource to add to collection (existing) add to new collection, remove from collection and add resources, are all designed to save console steps.

WDS Command prompt options to troubleshoot

WDS utilit to work from command prompt

 

C:\Windows\system32>wdsutil /allhelp

Windows Deployment Services Management Utility [Version 6.0.6001.18000]
Copyright (C) Microsoft Corporation. All rights reserved.

/Get-AllDevices                 Displays information on all pre-staged devices.
/Get-AllImageGroups             Displays information on all image groups.
/Get-AllImages                  Displays information on all images.
/Get-AllMulticastTransmissions  Displays attributes of all transmissions.
/Get-AllNamespaces              Displays attributes of all namespaces.
/Get-AllServers                 Displays information on all WDS servers.
/New-CaptureImage               Creates a WinPE image used for capturing
                                OS images.
/Disconnect-Client              Disconnects a client from a multicast
                                transmission or namespace.
/New-DiscoverImage              Creates a WinPE image used for WDS server
                                discovery.
/Add-Device                     Adds a pre-staged device.
/Get-Device                     Displays attributes of an existing device.
/Set-Device                     Changes attributes of an existing device.
/Add-Image                      Adds boot or install images.
/Copy-Image                     Copies an image within the image store.
/Export-Image                   Exports an image from the image store to a WIM
                                file.
/Get-Image                      Displays the attributes of an existing image.
/Remove-Image                   Removes a boot or install image.
/Replace-Image                  Replaces a boot or install image with a new
                                version.
/Set-Image                      Changes the attributes of an existing image.
/Get-ImageFile                  Displays information on images in a WIM file.
/Add-ImageGroup                 Adds an image group.
/Get-ImageGroup                 Displays information on an image group.
/Remove-ImageGroup              Removes an image group.
/Set-ImageGroup                 Changes the attributes of an existing image
                                group.
/Get-MulticastTransmission      Displays attributes of a a transmission.
/New-MulticastTransmission      Creates a new multicast transmission for WDS
/Remove-MulticastTransmission   Removes a multicast transmission for WDS Image.
/Start-MulticastTransmission    Starts a specified transmission.
/Get-Namespace                  Displays attributes of a namespace.
/New-Namespace                  Creates a new namespace.
/Remove-Namespace               Removes a namespace.
/Start-Namespace                Starts a specified namespace.
/Approve-AutoAddDevices         Approves pending auto-add devices of server.
/Reject-AutoAddDevices          Rejects pending auto-add devices of server.
/Get-AutoAddDevices             Displays auto-add devices on server.
/Delete-AutoAddDevices          Deletes devices in the auto-add device
                                database.
/Convert-RiPrepImage            Converts an existing RIS RIPrep image to a WIM
                                file.
/Disable-Server                 Disables all WDS services on a server.
/Enable-Server                  Enables all WDS services on a server.
/Get-Server                     Displays information on a WDS Server.
/Initialize-Server              Configures a WDS server for initial use.
/Set-Server                     Configures settings of a WDS server.
/Start-Server                   Starts all WDS services on a server.
/Stop-Server                    Stops all WDS services on a server.
/Uninitialize-Server            Reverts changes made during server
                                initialization.
/Update-ServerFiles             Updates server files on the REMINST share.
                                Image.
/Disable-TransportServer        Disables all WDS services on a Transport server.

/Enable-TransportServer         Enables all WDS services on a Transport server.
/Get-TransportServer            Displays information on a Transport Server.
                                Image.
/Set-TransportServer            Configures settings of a Transport server.
/Start-TransportServer          Starts all WDS services on a Transport server.
/Stop-TransportServer           Stops all WDS services on a Transport server.

To get help for specific command use:
     WdsUtil command /?

C:\Windows\system32>

-------------------
Thanks,