This VBS script will allow you to enter an SMS server name and site code as well as a machine name from a series of input dialog boxes. It will then look in the collection specified and determine if the machine name exist in the collection.
VBS Script:
strComputer = InputBox ("Enter SMS Server Name")
strSiteCode = InputBox ("Enter Site Code")
strResource = InputBox ("Enter Machine Name")
Set objWMIService = GetObject("winmgmts://" & strComputer & "\root\sms\site_" & strSiteCode)
' SMS_CM_RES_COLL_SMS00001 Is The All Systems Collection Change As Needed
Set colItems = objWMIService.ExecQuery("Select * From SMS_CM_RES_COLL_SMS00001 Where Name ='" & strResource & "'")
If colItems.Count > 0 Then
MsgBox UCase(strResource) & " Exist In The Collection"
Else
MsgBox UCase(strResource) & " Was Not Found In The Collection"
End If
This SQL server script will display machines with a specified percentage of free local disk free space available.
Select
SD.Name0 'Machine Name',
LD.DeviceID0 Drive,
LD.FileSystem0 'File System',
LD.Size0 'Total Drive Size',
LD.FreeSpace0 'Total Free Space',
LD.FreeSpace0 *100/ LD.Size0 'Percent Free'
From System_Disc SD, Logical_Disk_Data LD
Where SD.ItemKey = LD.MachineId
And LD.Description0 = 'Local Fixed Disk'
/* Change <xx Below To The Percentage Of Free Disk Space You Wish To Find.
Examples: <05 Will Return 5% Free And <10 Will Display 10% Free. */
And LD.FreeSpace0 *100/ LD.Size0 <20
Order By SD.Name0 Asc
When you install SMS 2003 Service Pack (SP) 3 not only will your SMS server(s) get the latest rollup of released SMS HotFixes but you will also gain full Microsoft Windows Vista compatibility. In addition it will also install the SMS Asset Intelligence.
SMS Asset Intelligence will provide you with several SMS Reports for Hardware, License and Software reporting. For a complete list see the post below:
New Asset Management Reports For SMS 2003 Service Pack 3
http://myitforum.com/cs2/blogs/dhite/archive/2007/05/06/new-asset-management-reports-for-sms-2003-service-pack-3.aspx
It will also make changes that will allow the Hardware inventory agent to collect additional information from your clients in what Microsoft calls “Artifact Data” that is exposed to the SMS console for querying.
It will also setup new asset lookup tables into SMS that are exposed to the SMS console and they are added as new classes to the SMS_Def.Mof file.
In System Center Essentials (SCE) 2007 you have the ability to have the SCE server email you the sites Daily Health Report similar the to "Computers" tab Report "Health Report” where you can have a summary of the sites resources status sent to you. This includes information for such things as inventory and alerts.
Whey you first install SCE you have the option to setup and configure the Daily Health Report with the Feature Configuration wizard as a post installation task. If you did not configure the Daily Health Report at that time or you did configure it and want to modify it for one reason or another can be easily accomplished.
Follow the steps below to setup or reconfigure the Daily Health Report.
1. From the “System Center Essentials 2007” program, group open the “System Center Essentials 2007 Console”
2. From the tool bar select “Go” and then select “Administration (Ctrl+6)” or use the shortcut key.
3. From the Administration leaf select “Settings”
4. In the middle "Settings" leaf double click on "Daily Health Report" from the Type: Server section to open the Server Settings – Daily Health Report task. In the “Do you want to receive the Daily Health Report?” Section Select “Yes” and then fill in the following information and then Select “Test” to test the configured settings:
Recipient Address:
SMTP Server:
Port:
Authentication Mode:
Send report daily at:
Example:
Recipient Address: DonHite@myITforum.Com
SMTP Server: Mail@mtITforum.Com
Port: 25
Authentication Mode: Anonymous
Send report daily at: 6:00 AM
5. When you have finished entering the configuration information select “Apply” then select “OK” to be returned to the Administration page.
This PowerShell script which is similar to my previous post entitled PowerShell Script To Create A New Organizational Unit will allow you to create new multiple Organizational Units (OU’s) based on names taken from a text file called NewOus.Txt rather than entering the new OU names one at a time.
Note: Be sure to change MyDomainName to your domain name and change Com if needed to reflect your sites naming.
PS1 Script:
$TextFile = GC -Path "C:\NewOus.Txt"
ForEach ($objItem in $TextFile){
$StrOUName = $objItem
$objDomain = [ADSI]"LDAP://dc= MyDomainName,dc=Com"
$objOU = $objDomain.Create("OrganizationalUnit", "ou=" + $StrOUName)
$objOU.setInfo()}
Write-Host "Your New OU's Have Been Created"
When we have two full moons in one month the second full moon is called a Blue moon.
Supposedly this term comes from the Farmers Almanac that began publication in 1818. Apparently in the Maine Farmers Almanac the editors listed the full moon dates for each month in Red. If there was a second full moon for that month it was in blue.
Since two full moons in one month are quite rare the term “Once in a blue moon” has come to refer to events that only happen rarely. For example once in a blue moon I actually do scratch off a winning lottery ticket.
The OpsMgr 2007 Agent Installation Account is an OpsMgr resource account with administrator privileges used to install its agent software on the resources you want to manage.
When you want to create a new managed computer resource this account is used to install the necessary software on the machine and that is why it needs to be an administrator account with elevated privileges on the managed resource. Because the account is encrypted before being used and then discarded after the installation it is a very secure way to install the agent software.
If you are a Hotmail user from the way back when days you could probably remember when you could use Microsoft Outlook to read your Hotmail. Then for some reason Microsoft dropped its MAPI support and when you attempted to configure Outlook to read it you told to go away.
Microsoft now has realized that perhaps they made a mistake removing MAPI support and with the Microsoft Office Outlook Connector Release Version 3 it is back. It works for Windows XP and Vista using either Outlook 2003 or Outlook 2007.
Download
http://www.microsoft.com/downloads/details.aspx?FamilyID=7aad7e6a-931e-438a-950c-5e9ea66322d4&DisplayLang=en
Note: Validation required prior to allowing you to download the file.
Download code samples and read the accompanying articles from the Office Developer Center.
Extending Excel Services Programmability Framework Samples
The SharePoint Server 2007 Sample: Extending Excel Services Programmability Framework Samples demonstrate how you can extend functionalities when working with SharePoint lists, query tables on Excel Services, external workbook references, SQL write-back, and user-defined functions (UDFs).
http://www.microsoft.com/downloads/details.aspx?familyid=c75a850f-b4bd-4b23-a43a-509a03590dd7&displaylang=en
Item-Level Auditing
This code sample shows you how to create an item-level auditing view programmatically in three different ways: using a custom SharePoint list, through the Excel client, and by manipulating the open XML file format to display auditing history using Excel Services on an application page.
http://www.microsoft.com/downloads/details.aspx?familyid=0e4dd1e7-4b1d-4cb1-b906-6d5d272c8e9d&displaylang=en
User-Defined Functions for Excel 2007 and Excel Services Sample Solution
The SharePoint 2007 Sample: User-Defined Functions for Excel 2007 and Excel Services Sample Solution contains sample user-defined functions (UDFs) and supporting files.
http://www.microsoft.com/downloads/details.aspx?familyid=e09fefbf-5fc7-44a7-9731-fd3dc41e5b9b&displaylang=en
Web Part That Calls Excel Web Services
This download contains a sample solution that demonstrates how to create a Web Part that calls Excel Web Services to perform custom calculations. It includes a deployment package sample that can be deployed to Microsoft Office SharePoint Server 2007.
http://www.microsoft.com/downloads/details.aspx?familyid=2c5919e4-0757-4db1-9798-e0e4032f12a8&displaylang=en
Setting Up a Development Environment for the 2007 Microsoft Office System
This code sample accompanies the MSDN technical article, "Setting Up a Development Environment for the 2007 Microsoft Office System." To view this article, click the link in Related Resources.
http://www.microsoft.com/downloads/details.aspx?familyid=a2f225fd-dfb8-4e2a-b0b5-2facd681541f&displaylang=en
This HTA script will display an analog clock for each of the United States time zones.
HTA Script:
<Html>
<Head>
<Title>US Time Zones</Title>
<Style>
Body {Background-Color: CornSilk}
</Style>
<Caption = Yes
Border = Thick
ShowInTaskBar = No
MaximizeButton = Yes
MinimizeButton = Yes>
<p><h3 align = center><font color='Orange'>Please Visit myITforum.Com</font></h3>
<div></div>
<Table Border = "0" Cellpadding = "3" Cellspacing = "3" Align = "center">
<Tr>
<Td><font color='brown'>Hawaii</font></Td>
<Td><embed src="http://www.clocklink.com/clocks/0001-yellow.swf?TimeZone=AHST&Place=&"
width="150" height="150" wmode="transparent" type="application/x-shockwave-flash"></Td>
<Td><font color='brown'>Alaska</font></Td>
<Td><embed src="http://www.clocklink.com/clocks/0001-red.swf?TimeZone=AKST&Place=&"
</Tr>
</Table>
<Td><font color='brown'>Pacific</font></Td>
<Td><embed src="http://www.clocklink.com/clocks/0001-gray.swf?TimeZone=PST&Place=&"
width="150" height="150" wmode="transparent"type="application/x-shockwave-flash""></Td>
<Td><font color='brown'>Mountain</font></Td>
<Td><embed src="http://www.clocklink.com/clocks/0001-blue.swf?TimeZone=MST&Place=&"
width="150" height="150" wmode="transparent"type="application/x-shockwave-flash"></Td>
<Td><font color='brown'>Central</font></Td>
<Td><embed src="http://www.clocklink.com/clocks/0001-green.swf?TimeZone=CST&Place=&"
<Td><font color='brown'>Eastern</font></Td>
<Td><embed src="http://www.clocklink.com/clocks/0001-orange.swf?TimeZone=EST&Place=&"
</script><Body>
<Span Id = "DataArea"></Span></Body><Div Align = "Center">
<P><A Href="http://myitforum.com/cs2/blogs/dhite">Created For myITforum By Don Hite</A>
Here you will find the Microsoft System Center Configuration Manager 2007 Client resources system requirements.
Supported Client Network Operating Systems (NOS)
Windows 2000 Advanced Server Service Pack 4 x86
Windows 2000 Datacenter1 Service Pack 4 x86
Windows 2000 Professional Service Pack 4 x86
Windows 2000 Server Service Pack 4 x86
Windows Embedded for Point of Service (WEPOS) x86
Windows Fundamentals for Legacy PCs (WinFLP) x86
Windows Server 2003 Datacenter Edition1 Service Pack 1 x86, x64 and IA64
Windows Server 2003 Enterprise Edition Service Pack 1 x86, x64 and IA64
Windows Server 2003 R2 Enterprise Edition x86, x64 and IA64
Windows Server 2003 R2 Standard Edition x86, x64 and IA64
Windows Server 2003 Standard Edition Service Pack 1 x86, x64 and IA64
Windows Server 2003 Web Edition, Service Pack 1 x86
Windows Vista Business Edition x86 and x64
Windows Vista Enterprise Edition x86 and x64
Windows Vista Ultimate Edition x86 and x64
Windows XP Embedded SP2 x86
Windows XP Professional for 64-bit Systems x64
Windows XP Professional Service Pack 2 x86
Windows XP Tablet PC SP2 x86
Mobile Device Client's
Windows CE 4.2 (ARM processor only)
Windows CE 5.0 (ARM and x86 processors)
Windows Mobile 5.0 Smartphone
Windows Mobile 6 Classic
Windows Mobile 6 Professional
Windows Mobile 6 Standard
Windows Mobile for Pocket PC 2003
Windows Mobile for Pocket PC 2003 Second Edition
Windows Mobile for Pocket PC 5.0
Windows Mobile for Pocket PC Phone Edition 2003
Windows Mobile for Pocket PC Phone Edition 2003 Second Edition
Windows Mobile for Pocket PC Phone Edition 5.0
Windows Mobile Smartphone 2003
The following are no longer supported
Windows 95
Windows 98
Windows Millennium Edition
Windows XP Media Center Edition
Windows XP Starter Edition
Windows XP Home Edition
Windows XP Professional, with less than Service Pack 2 applied
Windows Vista Starter Edition
Windows Vista Home Basic Edition
Windows Vista Home Premium Edition
Windows NT Workstation 4.0
Windows NT Server 4.0
Windows 2000 Server, Service Pack 3 and earlier
Windows 2003 Server, with no service pack installed
Windows CE 3.0
Windows Mobile Pocket PC 2002
Windows Mobile SmartPhone 2002
System Requirements
233 MHz Processor (300 MHz or faster recommended)
128 MB RAM (256 MB Recommended with 384 MB for OSD deployment)
Free Disk Space
350 MB available hard disk space for a new install
256 MB available hard disk space for an upgrade
Here you will find information on how to remove the SMS Client Health Tools from your SMS Site Server(s).
1. From the add and remove programs in the control panel select “Microsoft SMS 2003 Client Health Monitoring Tool” and click “Remove”
Note: You can also select “Click here for support information” and the Support Info dialog box will be displayed with information about the Microsoft SMS 2003 Client Health Monitoring Tool including the publisher and version information. Here you can also select “Repair” to correct any issues such as service issues.
2. When the uninstall has completed you need to manually remove the C:\Program Files\Microsoft SMS Client Health directory as it leaves the following:
C:\Program Files\Microsoft SMS Client Health\logs
chService.log
UIConfig.log
C:\Program Files\Microsoft SMS Client Health\TEMP
3. The Microsoft SMS 2003 Client Health Monitoring Tool program group is removed however the SQL database is not so you need to remove it as well as it leaves the Client Health database and all the tables listed below:
ClientHealthMPInfo
ClientHealthPingCurrent
ClientHealthPingHistory
ClientHealthPingSummary
ClientHealthPolicyHistory
ClientHealthPolicySummary
ClientHealthResults
You can remove the database manually or just remove the tables if you wish.
4. Run the following SQL query to delete the Client Health Database:
Use Master Drop Database Client_Health_Database_Name
This By Request VBS Script will allow you to open the Logs directory folder on a SMS site server in a semi-automated process by hard coding parts of the the Logs share name.
strLogsFolder = "SMS_" & strSiteCode & "\Logs"
Set objShell = CreateObject("Wscript.Shell")
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * From Win32_Share")
strCommand = "\\" & strComputer & "\" & strLogsFolder
objShell.Run strCommand