SQL Query To Find Unhealthy Machines

SQL Query:

 

Select Distinct

Name 'Machine Name',

LastUser 'Last Logged On User',

WasOnline,

LastPingResult State,

Classification Status

From ClientHealthResults

 

Where LastPingResult Is Not Null

And Classification = 'UnHealthy'

RoboCopy VBS Script

VBS script with source and destination folder input dialog boxes as well as hard coding the RoboCopy command line switches opposed to issuing the commands from the command prompt

 

 

 

Set objShell = CreateObject("Wscript.Shell")

 

objSource = InputBox("Enter Source")

objDestination = InputBox("Enter Destination")

 

objCommand = "RoboCopy.Exe " & Chr(34) & objSource & Chr(34) & " " & Chr(34) & objDestination & Chr(34) & " /e /r:1 /w:2"

objShell.Run(objCommand)

 

MsgBox "Done"

What's New in Configuration Manager 2007

Some aspects of Configuration Manager 2007 have changed very little since SMS 2003, while some have changed a lot. Also, several new features have been added and some features have been removed.

The following features are new to Configuration Manager 2007:

• Desired configuration management
  
• Network Access Protection for Configuration Manager
  
• Wake On LAN
  

The following features were previously available only in Feature Packs but are now incorporated into the core product:

• Mobile device management
  
• Operating system deployment
  
• Transfer site settings wizard
  
• Manage site accounts tool (MSAC)
  
• Asset Intelligence
  

The following features have changed significantly from SMS 2003:

• Backup and recovery
  
• Software updates
  

The following features have been improved but still function very much as they did in SMS 2003:

• The administrator console
  
• Collections
  
• Software distribution
  
• Software metering
  
• Remote tools
  

The following features either have not changed or have minor changes:

• Discovery
  
• Inventory
  
• Queries
  
• Reporting
  

The basic site infrastructure has not changed. You still have primary sites and secondary sites, although the new feature for software distribution called the branch distribution point might remove the need to create some child sites in your hierarchy. Site-to-site communication is still configured using senders and addresses; however, in Configuration Manager 2007 senders can be installed only on primary or secondary site server systems. Configuration Manager 2007 now supports hosting the site database on a clustered SQL Server virtual instance as well as SQL Server 2005 named instances. Several new server roles have been added to support new features.

In SMS 2003 you had two types of clients, but in Configuration Manager 2007 you have only one client type, which is similar to the SMS 2003 Advanced Client. Some of the client deployment methods have changed and some methods have been removed. A new method, software update point client installation, allows you to leverage your software update infrastructure to deploy Configuration Manager 2007 clients.

In SMS 2003 you had two security modes, but in Configuration Manager 2007 you have the equivalent of SMS 2003 advanced security. However, you now have two site modes: Configuration Manager 2007 native mode and Configuration Manager 2007 mixed mode. Although site modes are not at all related to the SMS 2003 security modes, they do involve the security of your Configuration Manager 2007 environment. Native mode is a requirement to support Internet-based client management, a new feature that allows you to manage clients that do not have a direct connection to your site.

In SMS 2003, the site server's local subnet is automatically used as the site boundary for the site during setup. In Configuration Manager 2007, there is no default boundary created during setup, and you must manually create the boundary for a site when setup has completed. In SMS 2003, there are site boundaries and roaming boundaries, but in Configuration Manager 2007, there is only one type of boundary and it is equivalent to SMS 2003 roaming boundaries. Computers are assigned as clients to Configuration Manager 2007 sites according to the site boundaries you configure in the Configuration Manager console. Boundaries can now be defined by IP subnets, Active Directory site names, IPv6 Prefix, or IP ranges.

In SMS 2003, roaming boundaries were either local or remote roaming boundaries. When creating Configuration Manager 2007 boundaries, you instead decide whether the boundary will be used for either a slow or unreliable or a fast (LAN) network connection. During upgrade, any existing remote roaming boundaries will become slow boundaries and any local roaming boundaries will become fast (LAN) boundaries.

In SMS 2003, you could not upgrade from the evaluation version of the product to the full version. Configuration Manager 2007 now supports upgrading from the evaluation version. When upgrading an evaluation version, whether it is SMS 2003 or Configuration Manager 2007, an entire setup process must be completed using the new installation source files.

In SMS 2003, the client push installation method properties used when installing clients have the default site code set to Auto. In Configuration Manager 2007, the default site code used when installing clients using the client push installation method is set to the site code of the primary site.

In Configuration Manager 2007, state messages are sent by Configuration Manager 2007 clients using a new messaging system built into the product that allows clients to send "checkpoints" of important changes of state. State messages are not the same as status messages; whereas status messages provide information about component behavior and data flow, state messages provide a snapshot of the state of a process at a specific time.

Configuration Manager 2007 also includes support for fully qualified domain names (FQDNs) and IPv6.

 

can be find more from.....http://technet.microsoft.com/hi-in/library/bb680807(en-us).aspx

Thanks,

Pavan Kumar

Status Check for Wake On Lan

On Error Resume Next

Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20

arrComputers = Array("ComputerName")
For Each strComputer In arrComputers
   WScript.Echo
   WScript.Echo "=========================================="
   WScript.Echo "Computer: " & strComputer
   WScript.Echo "=========================================="

   Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\WMI")
   Set colItems = objWMIService.ExecQuery("SELECT * FROM MSNdis_DeviceWakeOnMagicPacketOnly", "WQL", _
                                          wbemFlagReturnImmediately + wbemFlagForwardOnly)

   For Each objItem In colItems
      WScript.Echo "Active: " & objItem.Active
      WScript.Echo "EnableWakeOnMagicPacketOnly: " & objItem.EnableWakeOnMagicPacketOnly
      WScript.Echo "InstanceName: " & objItem.InstanceName
      ''WScript.Echo   " **Computer" & strComputer & "  WOL Settings Failed to Retrive"
     
   Next
Next

Dell recommend using SMS WOL BIOS Settings remote Enable

Dell recommend using SMS and Dell OpenManage Client Instrumentation (OMCI).  However, this requires WMI scripting which may be prevented if security lockdown settings prevent such scripts from running.

Pros: Exposes the Dell BIOS to WMI and therefore enables almost any modification to be made by running VB script.  It also means SMS hardware inventory can then report upon  BIOS settings by extending the SMS_DEF.MOF.

Cons: Requires agent software to be run on the client.

The Dell Client Configuration Utility (DCCU) can be used as an alternative to the OMCI client to create stand-alone executables that can output configuration settings ('Get Values') to an XML file and/or configure BIOS settings ('Set Values'), including enabling WOL.

Pros: Leaves not footprint on the client

Cons: An executable file needs to be created for every action you want to perform against the BIOS; meaning heavier network utilization.

BiosConfigUtility.exe

HP provides a number of tools based on HP Client Management Interface (CMI).  The exception is HP System Software Manager (SSM) which includes a bundled utility called BiosConfigUtility.exe that modifies BIOS settings through a text-based file format, which can be used independently of SSM.   HP says a future version of HP SSM will leverage HP CMI on 32-bit and 64-bit platforms.

Modify the DNS Server Search Order for a Network Adapter

Modify the DNS Server Search Order for a Network Adapter

Configures a TCP/IP-bound network adapter to use two DNS servers: 192.168.1.100 and 192.168.1.200. Note that even if a computer only uses one DNS server, the IP address of that server must still be passed to the SetDNSServerSearchOrder method as an array (in that case, an array with only one element).  and more Scripts can be found here

On Error Resume Next  strComputer = "." Set objWMIService = GetObject("winmgmts:" _     & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")  Set colNetCards = objWMIService.ExecQuery _     ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")  For Each objNetCard in colNetCards     arrDNSServers = Array("192.168.1.100", "192.168.1.200")     objNetCard.SetDNSServerSearchOrder(arrDNSServers) Next