Monday, November 30, 2009

Windows7 Taskbar Shortcuts

Windows Taskbar Shortcuts

+ T

Brings focus to the fi rst item in the taskbar. Press

again to cycle through each item.

+ # (1–9) If a program in the 1–9 slot is running, the

keystroke will launch it. If it is running with one

window, the same keystroke will switch to that

window. If it is running with multiple windows,

the keystroke will cycle between each thumbnail

of the open windows for that program. Aero

Peek will help you fi nd the right window.

(Note:

ALT+WinKey+# will open the corresponding

program's Jump List)

SHIFT + click on taskbar icon

Middle mouse button +

click on taskbar icon

Launches a new instance of a program

SHIFT + CTRL +

click on taskbar icon

Launches a new instance of a program in

elevated security mode

Middle mouse button +

click on


-------------------
Thanks,
Paddy

Tuesday, November 17, 2009

Why we need to Upgrade to SCCM 2007 from SMS2003 ?

Configuration Manager Feature Comparison Matrix Feature

SMS 2003

SCCM 2007

Administrative UI

Product Install

Good

Improved, Pre-requisite checking

Drag-and-Drop

No

Yes

Multi-select

No

Yes

Actions Pane

No

Yes

Preview Pane

No

Yes

Wizards

Some

Pervasive

Homepages

No

Yes

Icons

NT 3.51-style

High Precision

Folders

Only organizational, no replication

Organizational and Search Folders; replication to child sites

Operating System Deployment

End-to-end deployment

Yes1

Yes

Fully automated

No1

Yes

Wipe-and-load upgrade

Yes

Yes

Bare metal deployment w/PXE

Loose integration w/RIS

Built-in integration w/WDS

Side-by-side

BDD scripts

Yes, w/built-in SMP

Fully offline deployment

No1

Yes

Integrated Vista upgrade planning

No

Yes

Full server deployment

No

Yes

Security

Good

Much stronger

Flexibility/customizability

Good

Excellent

Vista/Windows Server 2008 compatibility

Good

Excellent2

Device driver management

No*

Yes

Boot Image Management

No*

Yes

Task Sequencing

Basic

Excellent

Asset Management

Asset Inventory

Good3

Much Improved

Integration with Usage Monitoring

No

Yes

Database Updates

Service Packs

Service Packs, Online Updates

Security and Configuration Management

Desired Configuration Management

No4

Yes

Pre-Defined Configuration Packs

No

Yes

Quarantine Support (NAP integration)

No

Yes

Manage over Internet

VPN Required

No VPN Needed

Smartphone/PDA Support

When Cradled

Wireless & Over-the-Air

Patch & Update Management

Good – Add-on pack

Excellent - Integrated with WSUS 3.0

Secure network storage of user state during Operating System deployment

 

No

 

Yes  

 

 

1 – Capable with the addition of the Business Desktop Solution Accelerator 2 – Windows Server 2008 Support requires System Center Configuration Manager Service Pack 1 or greater. 3- Asset Intelligence was introduced with SMS 2003 Service Pack 3 4- Desired Configuration Monitoring is a Solution Accelerator add-on to SMS 2003


-------------------
Thanks,
Paddy

Wednesday, October 28, 2009

How to Perform a ConfigMgr 2007 Site Reset

Provided here you will find the steps necessary to perform a ConfigMgr 2007 Site Reset if the need arises.

A site reset in Configuration Manager is similar to the process for SMS 2003 and can be performed in a matter of minutes. The site reset process is initiated using the CD-ROM Installation media or the Configuration Manager Installation directory folder on the site system with the issues that need resolved.

Follow the steps below to perform a ConfigMgr 2007 site reset using the Microsoft Configuration Manager Installation directory folder.

1. Locate the Setup.Exe in the following default location: “C:\Program Files\Microsoft Configuration Manager\bin\I386\Setup.Exe”

2. At the Welcome to the Microsoft System Center Configuration Manager 2007 Setup Wizard screen review the information on the screen and select “Next’ to continue.

3. At the Available Setup Options screen select “Perform site maintenance or reset this site” radial button and select “Next” to continue.

4. At the Site Maintenance screen select the checkbox to “Modify SMS Provider configuration” and select “Next” to continue.

5. From the SMS Provider Settings Modification screen ensure that the site server name is populated in the text box provided for you to “Enter the appropriate installation location for the provider” and select “Next” to continue.

6. Select “Yes” to continue at the popup dialog box that states:

“Specified installation for the provider is the same as the current provider location.

Would you like to reinstall the provider?”

At this point the proves is initiated and the Setup Action Status Monitoring screen is displayed with the following actions and their status:

Shutdown Configuration Manager Services
Reset ConfigMgr related accounts
Reset permissions for ConfigMgr related directories
Upgrade site control file
Update Registry
Verify permissions for ConfigMgr related directories

7. When the process has been competed select “Next” to continue.

8. At the Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard screen select the “View Log” button to review the log file and select “Launch the Configuration Manager Console after closing” to verify that ConfigMgr is operating as expected.

Note: If you choose not to review the log file at step 8 above you can review it at a later date. The site reset log file is appended to the existing C:\ ConfigMgrSetup.Log file.

Tip: Before performing a site reset it is a good practice to rename the existing ConfigMgrSetup log file to something like “Initial_ ConfigMgrSetup.Log” or “ConfigMgrSetup.Old” prior to performing a site reset. Then if needed you can rename the newly created site reset ConfigMgrSetup.Log file to something like “SiteReset_MMDDYY.Log”.

Advantages Of Performing An SMS 2003 Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2007/09/09/advantages-of-performing-an-sms-2003-site-reset.aspx

Specifying Your Own Password For The SMS Server Connection Account During A Site Reset
http://myitforum.com/cs2/blogs/dhite/archive/2006/12/04/specifying-your-own-password-for-the-sms-server-connection-account-during-a-site-reset.aspx

SQL Server 2008 Memory Support

In Microsoft SQL Server 2008 the Standard, Enterprise, Developer and Web editions can use whatever the Operating Systems maximum allowed memory is.

Windows Server 2003

Windows Server 2003 Standard Edition can use a maximum of 4 GB.

Microsoft Windows Server 2003 Enterprise Edition can use a maximum of 32 GB for 32-bit (x86) machines and 64 GB for 64-bit Itanium machines.

Windows Server 2008

Windows Server 2008 Standard Edition can use a maximum of 4 GB.

Microsoft Windows Server 2008 Enterprise Edition can use a maximum of 64 GB for 32-bit (x86) machines and 2 TB for 64-bit Itanium machines.

The Workgroup edition can also use the Operating Systems maximum on 32-Bit systems and 4 GB on 64-bit systems.

The Express and Express with Advanced Services can use a maximum of 1 GB.

Tuesday, October 27, 2009

If Patch is not getting install and in MBSA report it is showing as required

If Patch is not getting install and in MBSA report it is showing as required we can i dentify and troublshoot below steps:--

1) Microsoft Suggested to run the System redindence tool -- this tool is 130+MB file, This Kb Might required reboot
http://support.microsoft.com/kb/947821
and After installing check the log file %SYSTEMROOT%\Logs\CBS\CheckSUR.log
2)Take ownership of the Packages folder("%SYSTEMROOT%\Servicing\Packages") and add your account to have full control
3)Based on the log file will get the missing files list i.e., .MUM and .Cat files.
4)Copy the .MUM and .CAT files to the %SYSTEMROOT%\Servicing\Packages folder from other working system to Problem system "%SYSTEMROOT%\Servicing\Packages" Folder
5) After Copy the .mum and Cat files we need to restart the " Windows Modules Installer" Service
Install the Patch 974291, if it is not installing re-run the redindence tool and analize the log file
6) IMPORTANT: Change the ownership of the %SYSTEMROOT%\Servicing\Packages
folder back to 'NT Service\TrustedInstaller'
Ofcource for the above steps you should perfom with your process where Change / Downtime.

Monday, October 12, 2009

Hyper-V Server 2008 R2

Inherent Savings from Server Virtualization
Server consolidation Savings
Electrical Power Savings
Environmental Impact Savings
Space Savings
Getting started tools
MAP & HyperGreen
Extended benefits with Rapid Provisioning
Inherent Savings from Server Virtualization
Advantages of Microsoft’s Platform Approach
Lowering cost through Microsoft’s Innovative Licensing
Server consolidation Savings
Electrical Power Savings
Environmental Impact Savings
Space Savings
Approach

Free “Hyper-V Server 2008 R2” with High Availability
Built-in Windows Server 2008 Features
Hyper-V
High Availability
Energy Efficiency
More choice on hardware
Integrated Physical and Virtual Management
Savings and Training and Support


Tools

MAP & HyperGreen
Extended benefits with Rapid Provisioning
MAP 4.0

Monday, October 5, 2009

IPv6 & Windows Server 2008 - Overview:

"Although IPv6 addresses look nothing like IPv4 addresses, they do have their similarities. The biggest differences are that IPv4 addresses are 32 bits long, and IPv6 addresses are 128 bits long. Because of the excessive length of an IPv6 address, they are represented in an abbreviated form that will probably look completely foreign to anyone who has never used them before.
Any time a seasoned network administrator sees an address like 192.168.1.1, they instantly recognize it as an IPv4 address. This address contains four, eight bit numbers separated by periods. In order to understand how IPv6 addressing works, it is important to realize that when you see an IPv4 address, the address is being expressed in decimal form. This decimal form is a shortcut to expressing a 32 bit binary number. For example, the IP address 192.168.1.1 expressed in binary form looks like this:
11000000.10101000.00000001.00000001In the interest of saving space, I don’t want to get into how I did the conversion, but if you need help converting from a decimal number to a binary number, you can use the Windows Calculator.
IPv6 Addressing
Hopefully, my example above helps you to understand that even a simple IPv4 address is really long when you convert it to binary form. This problem is compounded when we start talking about IPv6 addresses though. Like an IPv4 address, an IPv6 address is an abbreviated form of a binary number. For example, here is what a 128 bit binary number looks like:
1111111010000000 0000000000000000 0000000000000000 0000000000000000 0000001000001100 0010100111111111 1111111001000100 0111111000111111When an IPv4 address is expressed in binary form, it is expressed in eight digit chunks called octets. Each of these octets corresponds to one of the numbers in the address (when it is displayed in digital for"

Friday, October 2, 2009

Howto: Edit network card bindings in Windows Server 2008

"Figuring out how to edit the order of NIC bindings on a Windows 2008 Server took quite a bit of Googling. It seems that you need to know a secret key combination to be able to view the Advanced tab, where the option to edit the NIC bindings is located.
To edit the network card binding order in Windows Server 2008:
Login to the server with administrative credentials
Click Start > Control Panel > Network and Sharing Center
On the left hand side select Manage network connections
Press Alt+N to display the Advanced menu
Select Advanced Settings. On the Adapters and Bindings tab, highlight your NIC and use the arrows on the right hand side to adjust it’s binding order.
You can also access the Network Connections screen directly by clicking Start > Run , typing ncpa.cpl and pressing Enter"

Using Winsat.exe in Windows Server 2008 as a performance benchmarking tool

"Microsoft has the Windows System Assessment Tool (Winsat) available for download that can assess a computer’s ability to run Windows Vista. This tool provides a wealth of information on you hardware’s horsepower, plus it’s scriptable. It’s designed to run under Windows Vista, but can be run under Windows Server 2008 as well. Here’s how to do it.
1. Dowload the Windows Vista Upgrade Advisor utility

2. Use Universal Extractor’s (uniextract) MSI method to extract the files from the .msi package

3. Copy winsat.exe to the c:\windows\system32 directory on the Windows 2008 server

4. Open an elevated command prompt and change to the c:\windows\system32 directory. There’s many different hardware components you can benchmark, but the following example benchmarks sequential reads on drive C:

winsat disk -seq -read -drive c

See the Technet command reference for Winsat for details on all tests winsat can perform, such as:


AssessmentDescription
winsat dwmAssesses the ability of a system to display the Aero desktop effects.
winsat d3dAssesses the ability of a system to run Direct 3D applications, such as games.
winsat memAssesses system memory bandwidth by simulating large memory to memory buffer copies.
winsat diskAssesses the performance of disk drives.
winsat cpuAssesses the performance of the CPU(s).
winsat mediaAssesses the performance of video encoding and decoding (playback) using the Direct Show framework.
winsat mfmediaAssesses the performance of video decoding (playback) using the Media Foundation framework.
winsat featuresEnumerates relevant system information.
winsat formalRuns a set of pre-defined assessments and saves the data in an XML fil"

Windows 2008 don;t show locked user Name

"Normally when a Windows workstation or server is locked, you’ll see something similar to the following Windows Security message:
This computer is in use and has been locked.

Only DOMAIN\USER (user name) or an administrator can unlock this computer.

To not show the name of the user who has locked a computer, the following can be defined in a workstation level GPO

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Display user information when the session is locked.

There are three choices if you enable this policy:

User display name, domain and user names (default setting)
User display name only
Do not display user information

Besides being able to apply this to Active Directory GPOs, this setting appears in the local security policy on my Windows XP SP3 VM. The setting is not available on my XP SP2 laptop, but I see from KB837022 there is a hotfix that corrects this problem in XP SP2.


Alternatively, the following DWORD can be created in the registry of XP SP2, Windows Vista, and Windows Server 2008 machine to accomplish the same thing:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system\DontDisplayLockedUserId

User display name, domain and user names = 1
User display name only = 2
Do not display user information =3

You need to restart the machine for the change to take effect.

You may also be interested in the related Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive logon: Do not display last user name setting. This security setting determines whether the name of the last user to log on"

Check windows uptime stats w/ Uptime.exe

"There is a very useful Windows command that Microsoft didn’t include in any version of windows but should have. This is the uptime command. There is a knowledge base article here. It was released back in the Windows NT days, but still works on all current versions of windows. I have found this to be an easy way to find out the uptime of the windows servers I maintain without have to log on to the box.

To install just download uptime.exe and place it in the windows directory. Then run it from the command line.

uptime /? will give a listing of all the options and uptime /help will give detailed instructions.
UPTIME, Version 1.01
(C) Copyright 1999, Microsoft CorporationUptime [server] [/s ] [/a] [/d:mm/dd/yyyy /p:n] [/heartbeat] [/? /help]
server Name or IP address of remote server to process.
/s Display key system events and statistics.
/a Display application failure events (assumes /s).
/d: Only calculate for events after mm/dd/yyyy.
/p: Only calculate for events in the previous n days.
/heartbeat Turn on/off the system's heartbeat
/? Basic usage.
/help Additional usage information.Uptime works by checking the windows event logs for startup and shutdown times. Running uptime with the /s switch will provide more detailed statistics as shown below. If the event log has been cleared or is corrupted uptime will not show correct stats.
I have found it helpful to set up .bat files with the servers I want to check. This then gives me a quick list of the uptime of various servers. It is quite a useful command. I’m not sure why Microsoft didn’t just stick it in the directory with all their other comma"

Thursday, October 1, 2009

WSH Scripting Tools

"WSH Scripting Tools
WSH Scripting Tools
ProductDescriptionProgrammer / ManufacturerDownloadPurchase
Admin Script EditorEditoriTripoli
ADSI ScriptomaticADSI query generatorScripting GuysFree
AxScripterIDEIEInspector Software LLC
BrineSoft Script EditorEditorBrineSoft
CodeLobsterEditorCodeLobster Software
EditPad LiteEditorJGSoftFree for non-commercial use
EditPad ProEditorJGSoft
HtaEditHTA editor/IDEAdersoft
HTA GeneratorHTA template generatorJ. LibensonFree
HTA HelpomaticHTA code generatorScripting GuysFree
(validation required)
JsEditJScript editor/IDEAdersoft
KS-Soft WMI ExplorerWMI browserKS-SoftFree
Log Parser 2.2Universal query tool to text-based data, Event Logs, Registry and Active DirectoryMicrosoftFree
Notepad++EditorNotepad++ teamFree
(donations welcome)
OLE/COM Object ViewerObject browser & testerMicrosoftFree
(validation required)
OnScriptIDEXLnow
PrimalScript Scripting IDE (Standard, Professional & Enterprise Editions)IDESapien
PSPadEditorJan FialaFree
(donations welcome)
Sapien WMI ExplorerWMI browserSapien TechnologiesFree
Script Debugger (NT 4 & later)WSH debugging environmentMicrosoftFree
(validation required)
Script Debugger (Win98/Me)WSH debugging environmentMicrosoftFree
(validation required)
Script Debugger IDEIDEStas Semenov
Script EncoderEncode your scriptsMicrosoftFree
(validation required)
ScriptomaticWMI query generator & testerScripting GuysFree
(validation required)
String-O-MaticConvert, escape, unescape, encode & decode stringsAlex K. AngelopoulosFree
System Scripting RuntimeRun scripts as servicesFranz Krainer
SystemScripterEditorScriptInternals.com
Term-O-MaticModified version of the Scriptom"

How to Configure Windows Server 2008 for Site Systems

How to Configure Windows Server 2008 for Site Systems: "How to Configure Windows Server 2008 for Site SystemsUpdated: April 1, 2009
Applies To: System Center Configuration Manager 2007
When Configuration Manager 2007 SP1 site systems will be installed on Windows Server 2008 computers, additional configuration changes might be required to ensure successful installation and operation.
The procedures in this topic can be used to configure Windows Server 2008 to support Configuration Manager 2007 SP1 site system installation.
To Install Internet Information Services (IIS) to support Configuration Manager 2007 SP1 site systems on Windows Server 2008 Computers
This procedure describes how to install Internet Information Services (IIS) 7.0 Windows Server 2008 to support the following site system roles:
Management point.


Background Intelligent Transfer Service (BITS)-enabled distribution point.


Reporting point.


Software Update Point.


Server locator point.


Fallback status point.


To install and configure WebDAV for IIS 7.0 to support management point and BITS-enabled distribution point site system computers
Because WebDAV IIS extensions required for the management point and BITS-enabled distribution point site system roles are not installed by default with IIS 7.0, WebDAV extensions must be manually installed and configured after installing IIS 7.0.
To add Remote Differential Compression for site server and branch distribution point computers
If a site system will be used only to host the site server or branch distribution point site system roles, IIS is not required. However, site servers and branch distribution point site systems require Remote Differential Compression (RDC) to generate package signatures and perform signat"

ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY

**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY
This error is found on secondary servers running Microsoft System Center Configuration Manager (SCCM or ConfigMgr) 2007 SP1.

Solution is similar to John Marcum's post here

Error from mpfdm.log:
Verifying local MP outbox directory E:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\AIKbMgr.box for Asset Intelligence KB Manager exists... SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 240 (0x00F0)
**ERROR: Cannot find path for destination inbox Asset Intelligence KB Manager on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 240 (0x00F0)
Worker thread [Asset Intelligence KB Manager] cannot update environment so skiping outbox processing. SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 240 (0x00F0)
Updating environment... SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 2272 (0x08E0)
Verifying local MP outbox directory E:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\amtproxy.box for SMS_AMT_PROXY_COMPONENT exists... SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 2272 (0x08E0)
**ERROR: Cannot find path for destination inbox SMS_AMT_PROXY_COMPONENT on server REGISTRY SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 2272 (0x08E0)
Worker thread [SMS_AMT_PROXY_COMPONENT] cannot update environment so skiping outbox processing. SMS_MP_FILE_DISPATCH_MANAGER 7/16/2009 11:25:19 AM 2272 (0x08E0)
Updating environment... SMS_MP_FILE_DISPATCH_MANAGE"

Wednesday, September 30, 2009

Difference between bat and cmd

"I've occasionally thought on the difference between cmd and bat, and from an execution point of view I didn’t think there was any. But it turns out a few commands can modify the execution path of batch files, because they modify the errorlevel differently based on whether they were executed as a .bat or .cmd.

The comment that I did find from Microsoft (the source was MZ according to the signature block!)

The differences between .CMD and .BAT as far as CMD.EXE is concerned are: With extensions enabled, PATH/APPEND/PROMPT/SET/ASSOC in .CMD files will set
ERRORLEVEL regardless of error. .BAT sets ERRORLEVEL only on errors.


If you save the text below as test.bat and test.cmd, and then run each from a command prompt, you see two different results. Note that command extensions are enabled by default on XP, a requirement for this behavioural difference.

I saw several references to bat running under 16-bit VDM and cmd running under 32-bit when executed from a shortcut, however I couldn’t reproduce this on XP SP2.

In addition, apparently 9x days and before there was only bat? And then with NT CMD was introduced, and running the same .bat file on 9x and NT definitely had different results, so having two different extensions made it less likely to accidently run a cmd written for NT on a 9x box if you were interoperating between the two. This sounds plausible, but I can't remember those sorts of details that far back.

I hope this doesn’t excite anyone.



::
:: When called from a cmd, 'set' resets errorlevel, whereas when called from a bat the errorlevel from the previous command is returned.
:: The four examples below show this in different ways, two calling a subrou"

Monday, September 28, 2009

Testing management points the Configuration Manager 2007 way - Jeff Gilbert's Web blog at myITforum.com

Testing management points the Configuration Manager 2007 way - Jeff Gilbert's Web blog at myITforum.com: "Testing management point connectivity is just one of those things that SMS/ConfigMgr admins need to do on a regular basis. You can always peruse the mpcontrol.log to check management point health, but to make it easier, the product team has provided some handy test urls that can be used instead of reviewing the mpcontrol.log all the time.
Using the management point test urls is a pretty old tip. It's documented in a ton of places including the SMS 2003 FAQ, the Configuration Manager 2007 documentation, and a myriad of other Web locations. However, there is a catch when using these test urls in Configuration Manager sites that may not seem obvious at first and is a change from SMS 2003 behavior. I noticed this while working on something in my lab so I figured it would be a good tip to pass along.
When testing management point connectivity in SMS 2003 sites, you just open up a Web browser instance and go to: http:///sms_mp/.sms_aut?mplist. If all is well with the management point you will see:




(Yes, I know there's nothing there...that's a good thing for SMS 2003 sites and what you should see if the management point is responding to http requests )
In Configuration Manager sites, you actually do see something when you browse to the test urls and Don Hite has done a nice job documenting some of that behavior in his blog already.
So, in SMS 2003 sites, seeing nothing is good and something (IIS errors) is bad. In Configuration Manager sites, seeing something is good and nothing (IIS errors) is bad...that sounded a lot clearer in my head.
Anyway, moving on. If you browse to that"

SCCM 2007 R3

"Announcing System Center Configuration Manager 2007 R3
Today, the System Center team is excited to share with you our plan to release System Center Configuration Manager 2007 R3. This new release of the ConfigMgr is packed with some extremely cool features, which over the coming months we plan to share with you in different ways.
Recent shifts in the world economy have brought new focus on IT departments, and also to technology investment. Organizations are being pressured to do more with less, while at the same time manage an increasing range of working scenarios, mobility requirements, and business demands. Through all of this, they need to maintain security levels, answer compliance challenges and address the growing Green IT landscape.
As organizations look to reduce financial costs and environmental impacts, power management is proving to be a successful approach. The payback for power management is clear – when a PC is using less power it translates directly into reduced operational costs – either directly through reduced energy consumption or from a growing number of electrical companies that offer rebates to companies that can prove enforcement of centralized power management policies. In addition, continuous PC power management pays environmental dividends measured in terms like Kwh, or CO2 emissions savings.
Forrester estimates that more than 90% of firms are implementing or considering PC power management. Despite the advanced capabilities provided in Windows Vista and Windows 7, The U.S. Environmental Protection Agency estimates that no more than 10% of all enterprise PCs in use have their power management capabilities turned on today. Without centra"

System Center Configuration Manager 2007 | “Announcing System Center Configuration Manager 2007 R3” - Blog de Aurélien BONNIN [EXAKIS]

System Center Configuration Manager 2007 R3

There are a few areas of focus for ConfigMgr R3, with the main engineering effort concentrating on Power Management. Here are the goals for this feature:
Power Management
The goal of this capability is to enable Configuration Manager to further reduce the operational costs of IT by providing basic power management features native to the product. Our approach is based on 3 primary areas:
A. Help the organization plan a power strategy by monitoring current power state and consumptions and reporting on machine utilization trends, current power settings and current energy consumption
B. Enable the Administrator to easily create, deploy and enforce specific power settings using the existing ConfigMgr infrastructure
−Ability to set peak and non-peak schedules
−Ability to remediate settings if changed
−Ability to opt out machines from power policy
C. Provide the business meaningful report formats that are relevant to Power Management
An effective approach to power management needs to maximize power policy deployment while minimizing the impact to the end-user. System Center Configuration Manager helps customers further reduce their operational costs by adding new in box capability to their ConfigMgr infrastructure, and by seamlessly enabling power management client agent services to their existing Collection landscape.
In addition to power management, ConfigMgr R3 will provide customers with enhanced scale and performance support above current numbers.

Friday, August 14, 2009

JAI HIND JAI HIND

               JAI H
               JAI HIN JA
                JAI HIND JAI HI
                  JAI HIND JAI H
                JAI HIND JAI HI
                 JAI HIND JAI
                 JAI HIND JAI
                   JAI HIND JAI
                   JAI HIND
                   JAI HIND J
                  JAI HIND JAI H
                JAI HIND JAI HIN
               JAI HIND JAI HIN                                  JAI H
             JAI HIND JAI HIND J                               JAI HIND J
            JAI HIND JAI HIND JAI H                 J         JAI HIND J
       JAI HIND JAI HIND JAI HIND JAI              JA     JAI HIND JAI
      JAI HIND JAI HIND JAI HIND JAI HIND J        JA      JAI HIND
       JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND JAI HIN
        JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND J JAI HIND JAI

         
JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND  JAI HIND JAI
  JAI HI JAI HIND JAI HIND JAI HIND JAI HIND JAI HIN        JAI HI
 JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND      JAI H
     JAI HIND JAI HIND
JAI HIND JAI HIND JAI HIND JAI        JAI
   
JAI HIND JAI HIND JAI HIND JAI HIND JAI HIND JAI HIN        J
     JAI HI JAI HIND JAI HIND JAI HIND JAI HIND JAI
      JAI H JAI HIND
JAI HIND JAI HIND JAI HIND J
             JAI HIND
JAI HIND JAI HIND JAI HIND
            JAI HIND JAI HIND JAI HIND JAI HIND
             JAI HIND JAI HIND JAI HIND JAI
             JAI HIND JAI HIND JAI HIND JAI
             JAI HIND JAI HIND JAI HIND J
             
JAI HIND JAI HIND JAI HIND
             JAI HIND JAI HIND JAI HIN
              JAI HIND JAI HIND JAI HI
               JAI HIND JAI HIND JA
               JAI HIND JAI HIND J
                JAI HIND JAI HIN
                 JAI HIND JAI HIN
                 JAI HIND JAI HI
                  JAI HIND JAI H
                   JAI HIND JAI
                   JAI HIND JAI
                   JAI HIND JAI
                     JAI HIND
                     JAI HIN
                      JAI HI
                       JAI H
                        JAI

'VBS Script To Send A Remote Machines Hot Fix Information To Excel


'VBS Script To Send A Remote Machines Hot Fix Information To Excel
strComputer = InputBox ("Enter Machine Name")

 

Set objExcel = CreateObject("Excel.Application")

objExcel.Visible = True

objExcel.Workbooks.Add

intRow = 2

 

objExcel.Cells(1, 1).Value = "Machine Name"

objExcel.Cells(1, 2).Value = "Hot Fix ID"

objExcel.Cells(1, 3).Value = "Description"

objExcel.Cells(1, 4).Value = "Install Date"

 

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set colItems = objWMIService.ExecQuery("Select * from Win32_QuickFixEngineering Where HotFixID <> 'File 1'")

For Each objItem In colItems

objExcel.Cells(intRow, 1).Value = UCase(strComputer)

objExcel.Cells(intRow, 2).Value = objItem.HotFixId

objExcel.Cells(intRow, 3).Value = objItem.Description

objExcel.Cells(intRow, 4).Value = objItem.InstalledOn

 

intRow = intRow + 1

Next

 

objExcel.Range("A1:D1").Select

objExcel.Selection.Interior.ColorIndex = 19

objExcel.Selection.Font.ColorIndex = 11

objExcel.Selection.Font.Bold = True

objExcel.Cells.EntireColumn.AutoFit

 

MsgBox "Done"

 

Tuesday, August 11, 2009

Collection of Computers based on Users

Collection of Computers based on Users

 
SMS has a nice feature that allows you to create a collection based on users. That way when a users logs into a computer SMS will then run an advertisement for whatever computer they are on. The problem is maybe you want to have a collection of computers not the users. The worst flaw this the collection query I have created below and using collections based on users is that if a person logs in to another machine, for whatever reason, SMS will find them and push software to them.
That in mind, here is a collection that will take any OU group of users and create a collection of computers.


---------------------------------------
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 inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.UserName in (select UniqueUserName from SMS_R_User where UserOUName = "xxxx /SECURITY USERS & GROUPS" )
--------------------------------------
Windows User account and group discovery must be enabled and run on your server to use this.

How does this work. It first grabs the list of users. Then matches them to the comptuers that SMS currently sees them logged into. To change this to Last Logged in user you need to change the SMS_G_System_Computer_System to SMS_R_System.LastLogonUserName for computers. This will give you last logged in user.

"Limit to Collection" for all your computer Workstations or further limit it to based on departments

If you don't know what group then you can create a query of just (select UniqueUserName from SMS_R_User where UserOUName = "") click values until you have the value you need and paste it into the larger query.
-------------------
Thanks,
http://sccm07.blogspot.com/

Tuesday, August 4, 2009

ALL MY recommendations to become a expert on 2k3 Server

Task 1
Links and comments
AD Basics 
AD basicthings to be know --Troubleshooting Active Directory
Common Windows Administrative Tasks
 
Backing up and restoring data
 
Changing group memberships
 
Checking event logs
 
Creating administrative scripts
 
Creating logon scripts
 
Creating user and group accounts
 
Deploying and upgrading software
 
Installing a DHCP server
 
Installing a domain controller
 
Managing applications on a local computer
 
Managing applications remotely
 
Managing directory replication
 
Management tasks for disks and volumes
 
File and folder management
 
Managing network printers
 
Managing servers remotely
 
Managing services
 
Monitoring network traffic
 
Monitoring security-related events
 
Monitoring server performance
 
Resetting user passwords
 
Safeguarding your system
 
Scheduling tasks
 
Setting up DNS
 
Setting up TCP/IP
 
Setting user and group security
AD FRS Basic and Troubleshooting
Troubleshooting Active Directory Replication Problems
 
High-level Methodology for Troubleshooting Active Directory Problems 
Troubleshooting High CPU Usage on a Domain Controller
Troubleshooting Active Directory—Related DNS Problems 
Performance and Reliability Monitoring 
System Recovery and Troubleshooting 
Manage Operations Master Roles
Securing Active Directory
How do you say AD and DNS integrated...What do you mean by this?
Understanding the Global Catalog
Understanding Sites and Replication and when to implement a site
Manage Forest Trusts & Creating
Manually publish a printer in Active Directory
Checklist: Creating a new Forest / New Domain / Child Domain Tree

Enjoy,
-Paddy