July 2006 - Posts

Microsoft Acquisitions

 

The list of Microsoft company purchases keeps growing but this year seems to be a boon year for Microsoft acquisitions. Winternals and Sysinternals are not the only ones purchased by Microsoft this year but for some reason these acquisitions seem to be hitting a nerve among Windows Server, SMS Server and the MOM Server user communities. 

 

This year alone Microsoft has acquired not only Winternals and Sysinternals but Softricity, Whale Communications, Massive Inc., Lionhead Studios, ProClarity Corp, Apptimum Inc., Onfolio Inc. and Motion Bridge as listed on their official Investor relations page below:

 

http://www.microsoft.com/msft/acquisitions/history.mspx#EV

 

Microsoft again announced last week that it is purchasing Azyxxi software which is a healthcare data aggregation software package built on SQL Server and .Net technologies. But what do all these Microsoft purchases and acquisitions mean to us the “Microsoft user’s community”?

 

This is not a new practice for major software companies in fact it is an old practice. I can remember how angry I was when my favorite MS-DOS utilities suite "Norton Utilities" was taken over by Symantec when they “Merged” with Peter Norton Computing in 1990. The same thing happened again when my  favorite MS-DOS file manager Xtree was purchased by Central Point software the makers of PC Tools in 1993 which by the way was then acquired by Symantec as well within months of the Xtree “Merger”.

 

I was upset because I thought it was a way for Symantec and Central Point to effectively eliminate their rival competition. Furthermore I was afraid that Central Point or Symantec would release their versions of the software that they acquired and change them so much that they would barely be recognizable as my old favorites and I would no longer care to use them.

 

This practice or strategy seems to be especially true for Microsoft who has consistently bought or acquired companies for the last 20 years. I have heard both the negative and the positive arguments for and against Microsoft acquiring small to medium sized companies and most of them ring true from both sides of the coin.

 

What do you think about mergers and acquisitions as a whole or acquisitions by Microsoft in particular? Are acquisitions and mergers a good thing or a bad thing?

Is it just a way for larger companies to eliminate their competition or is it a means in which companies can legitimately obtain the intellectual properties of companies for their own purposes?

 

Additional Resources:

 

Wikipedia List of companies acquired by Microsoft Corporation:

 

http://en.wikipedia.org/wiki/List_of_companies_acquired_by_Microsoft_Corporation

 

 

Posted by dhite | 2 comment(s)
Filed under:

Retrieving Dynamic Link Library Version Information From A Remote Machine

 

Use the following Vbs script to get the file name, manufacturer and version of a .Dll (or any other file for that matter) file from a remote machine.

 

In the example below we are getting the Name, Version and Manufacturer for the C:\Windows\System32\Wbem\WbemCore.Dll.

 

Note: In the script below notice that the path noted above has not one but two forward slashes (\\) to return the absolute path for the file you are querying.

 

Vbs Script:

 

strComputer = InputBox ("Enter Machine Name")

Set objWMIService = GetObject("winmgmts:" _

    & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")

Set colFiles = objWMIService.ExecQuery _

    ("Select * from CIM_Datafile Where name = 'C:\\Windows\\System32\\Wbem\\WbemCore.Dll'")

For Each objFile in colFiles

Wscript.Echo "Name: " & objFile.Name

Wscript.Echo "Version: " & objFile.Version

Wscript.Echo "Manufacturer: " & objFile.Manufacturer

Next

 

Posted by dhite | with no comments
Filed under:

Searching Your SQL Database Views And Procedures For Specified Text

 

In response to my post “Searching Your SQL Database for A Specified Column Name” I wrote a follow up article entitled ”Searching Your SQL Database For A Specified Column String” since as I mentioned in that post several people asked me if it is possible to go further into the SQL database to find not just a specified column header but actual SMS captured data such as an individual user or computer name.

 

I answered that question in the Searching Your SQL Database for a Specified Column String post and that article too generated several e-mail inquiries. Some people asked if you could look for specific text (String) in a View and still others asked if it was possible to search procedures as well.

 

Unlike the Searching Your SQL Database for a Specified Column String solution this is actually quite easy to accomplish for both Views and Procedures. I created the query to look for both qualifiers in order to kill two birds with one stone as the saying goes.

 

I also added a Case statement to the SQL query below to make the results set for SysObjects.XType easier to understand so you can look in the ‘Views’ or ‘Stored Procedures’ leaf of the SQL Enterprise Manager (SEM) for the appropriate Name as defined in the location output.

 

Note: The SysComments.Text column is an NvarChar data type with a size of 4000 characters and contains the actual syntax that you would see in the SEM if you were to right mouse click on a view or stored procedure and select the ‘Properties’ tab.

 

To use the SQL query below change the line Where Text Like '%UserName%'

from '%UserName%' to the string that you want to search for. As was mentioned in my original post the percent symbols are set to function as wildcard placeholders. You can either retain the percent symbols or remove one or both of them as you wish.

 

To run or execute the SQL query below simply copy and paste the SQL query below into the SQL query analyzer (Isqlw.Exe from the start > run line) use the database dropdown arrow to select your SMS database change the ‘Where Text Like’ line to the keyword that you wish to locate and press the F5 keyboard shortcut to start the query parser.

 

SQL Query:

 

Select  

SysObjects.Name Location,

 

'Object Type' = Case

When SysObjects.XType = 'P' Then 'Procedure'

When SysObjects.XType = 'V' Then 'View'

Else ''

End

 

From SysComments

Join SysObjects on SysComments.Id = SysObjects.Id

 

Where Text Like '%UserName%'

And SysObjects.XType In ('P', 'V')

 

Group by SysObjects.Name, SysObjects.XType

 

Posted by dhite | with no comments
Filed under:

SMS Administrators Console User Interface Log File

 

When you install SMS 2.0 or SMS 2003 a logs folder is created in the %WinDir%\ SMSAdmin directory. The AdminUi.Log file is where the SMS Administrator Console logs its operations.

 

For SMS console connectivity issues this is the place to look first. A successful connection will include the following. Notice that the last line states that the “connection succeeded” and all is operating as expected.

 

  • Setting connection to NameSpace:\\ServerName\root\sms\site_XXX

 

  • Info(ConnectServer):Connecting to server:namespace \\ServerName\root\sms\site_XXX

 

  • Info(ConnectServer): Connecting to server. Network: \\ServerName\root\sms\site_XXX

 

  • SiteCode XXX - SiteServerName ServerName, Provider Version: 2.50.4160.2000

 

  • SiteBuildNumber is 4160

 

  • Set the connection succeeded.

 

If you have issues connecting to the Site server the AdminUi.Log will provide you with enough information to troubleshoot the issue(s) at hand.

 

A “Connection Failed” status might include the following in the AdminUi.Log file:

 

  • Info(ConnectServer):Connecting to server : namespace \\ServerName\root\sms

 

  • Info(ConnectServer):Connecting to server. Network : \\ServerName\root\sms

 

  • Error(ConnectServer):Possible UI connection error code is -2147023174 [0x800706ba]

 

Tip:

 

When troubleshooting SMS Console connectivity issues you can make a copy of the AdminUi.Log file or rename it to AdminUi.Old and it will be recreated. This will make it easer to troubleshoot and may save you time especially if you are not using SMS trace to view your Log files.

 

Posted by dhite | with no comments
Filed under:

The First IBM Personal Computer Turns 25

The first IBM Personal Computer (PC) the IBM model 5150 was announced 25 years ago this August 2006 at a press conference in New York on August 12, 1981. It was developed by a group of engineers and designers from the IBM Entry Systems Division in Boca Raton Florida under the direction of Don Estridge (1937–1985) known as the "Father of the IBM PC". It was soon available for purchase in the fall of that same year.

It featured an Intel 8088 4.77 MHz microprocessor and came equipped with 16K of RAM expandable to 640K. It operated on IBM PC-DOS Version 1.0 which was developed by Microsoft and they in turn licensed it to IBM as PC-DOS.

The display was 80 X 24 text and it boasted an optional 160K 5.25 floppy disk drive and came equipped with a port for its keyboard and cassette drive. The unit as a whole could be purchased for about $3000.00 US. By the following year IBM sold more than 50,000 units.

Before the 5150 was introduced IMB developed a micro-computer the IBM 5100 (Project Mercury) in 1975 but it was not nearly as successful as the 5150. This is in part due to the fact that it retailed for $15000 US. The 5100 may in fact be the very first entirely self contained portable computer system that did not require an entire room to house it.

Prior to this in 1967 IBM created the first 8 inch floppy disk or "Memory Disk" which could hold 80KB of data as a system for loading information into their System-370 mainframe units. It was not until 1973 that IBM introduced the sealed IBM 3340 hard disk unit commonly called the Winchester disk system designed by IBM’s Kenneth Haughton. Because the 3340 had twin 30 MB spindles Haughton named it after the Winchester 30-30 rifle.

For more information:

The IBM PC's debut

IBM Exhibits By Subject

Don Estridge

Posted by dhite | with no comments
Filed under:

The SQL Server 2005 Tools Menu

 

Depending on how you installed SQL server 2005 you may have some or all of the following “Microsoft SQL Server 2005” program group menu shortcuts.

 

Note: Most of the shortcuts that follow are installed when you add the many SQL Server 2005 “Optional” components. 

 

Business Intelligence Development Studio

 

This is where you will find tools available to manage your SQL database. Here you can perform most of the tasks that you were able to do in SQL 2000’s Enterprise Manager (SEM). For example you can create queries, modify objects start additional components such as Reporting Services, Analysis Services and Integration Services (old DTS or Data Transform Services).

 

Database Tuning Advisor

 

The database tuning advisor replaced the Index Tuning Wizard and allows you to monitor sessions on your database where you will be given suggestions to improve your database operations.

 

Profiler

 

The SQL profiler allows you to troubleshoot database component performance. It works by capturing and recording database activity to be saved and examined at a later time. It is good for creating baselines as snapshots in time.

 

Report Manager

 

The report manager is the web interface for your SQL reporting services. Here you can manage your applications and set security and configure its various components. Database users as opposed to database administrators can view the various reports that you have created and export them if the security has been set for them to do so.

 

SQL Computer Manager

 

Here is where you can configure your network libraries and various maintenance tasks.

 

SQLServer Books Online

 

Here is where you find the “Manual” as it were for SQL server 2005 or the books on line (BOL).

 

SQL Server Management Studio

 

This is the replacement of the SQL enterprise manager (SEM) the Query analyzer (ISQLW) and the Analysis Services Manager (ASM). You can manage your database objects and can create queries as well as the various other tasks previously available to you from the SEM.

 

Posted by dhite | with no comments

Modifying My Excel Vbs Scripts To Save Output As An Excel Spreadsheet

 

As a rule of thumb I create my Excel Vbs scripts to open the script output in excel and give the user the option of saving the file themselves or discarding it entirely.

 

If you want to modify any of my Excel Vbs scripts to automatically save the output as a named Excel spreadsheet here you will see how to make the modifications for yourself.

 

Most of my Excel scripts begin as such

 

Set objExcel = CreateObject("Excel.Application")

objExcel.Visible = True

objExcel.Workbooks.Add

intRow = 2

 

To save the file automatically add the following before the line that reads: intRow = 2

 

Set objWorkbook = objExcel.Workbooks.Add()

Set objWorksheet = objWorkbook.Worksheets(1)

 

You will now have the following:

 

Set objExcel = CreateObject("Excel.Application")

objExcel.Visible = True

objExcel.Workbooks.Add

Set objWorkbook = objExcel.Workbooks.Add()

Set objWorksheet = objWorkbook.Worksheets(1)

intRow = 2

 

At the end of the script add the following:

 

Wscript.Echo "Complete"

objWorkbook.SaveAs "DriveLetter\FolderName\FileName.xls"

objExcel.Quit

 

This will display the message “Complete” to let you know the script has reached its conclusion. Then the file will be saved as you have specified and the last line will close Excel.

 

Posted by dhite | with no comments
Filed under:

Useless Historical Trivia

 

  • In the mid 1500's mattresses were secured on bed frames by ropes. When you pulled on the ropes the mattress tightened, making the bed firmer to sleep on. Hence the phrase "goodnight, sleep tight."

 

  • It was the accepted practice in Babylon 4,000 years ago that for a month after the wedding, the bride's father would supply his son-in-law with all the mead he could drink. Mead is a honey beer and because their calendar was lunar based, this period was called the honey month, which we know today as the "honeymoon".

 

  • In English pubs, ale is ordered by pints and quarts... So in old England, when customers got unruly, the bartender would yell at them, "Mind your pints and quarts, and settle down." It's where we get the phrase "mind your P's and Q's"

 

  • Pope Gregory was the one most commonly given credit for the "God Bless You" response to a sneeze. During the plague of 590 AD. Pope Gregory ordered unceasing prayer for God's intercession. Anyone sneezing at that time was immediately blessed ("God bless you") to combat the possibility of the person developing the plague.

 

  • If a statue in the park of a person on a horse has both front legs in the air, the person died in battle. If the horse has one front leg in the air the person died as a result of wounds received in battle. If the horse has all four legs on the ground, the person died of natural causes.

 

  • In the 1400's a law was set forth that a man was not allowed to beat his wife with a stick no thicker than his thumb. Hence we have "the rule of thumb"

 

  • Many years ago in England, pub frequenters had a whistle baked into the rim, or handle, of their ceramic cups. When they needed a refill, they used the whistle to get some service. "Wet your whistle" is the phrase inspired by this practice.

 

 

Posted by dhite | 1 comment(s)
Filed under:

The 66th Annual Sturgis Motorcycle Rally

The 66th annual Sturgis motorcycle rally is set to begin on August 7th and will “run” until the 13th of August in Sturgis South Dakota. My days of riding the black hills (On a Sportster of course!) are long gone and it is up to my kids to carry on for me.

This year I am taking a long needed vacation that week to watch my Grandson and his half sister as the kids make the long ride to my old stomping grounds.

This larger than life annual event began back in 1938 when J.C. Hoel known as “Pappy” invited a small group of 9 motorcycle racing enthusiast to camp in his yard. The group called themselves the “JackPine Gypsies Motorcycle Club”.

The first Black Hills Motor Classic consisted primarily of in state motorcycle racers who camped in the city park. It was a family oriented event much like it is today but on a much larger scale.

If you are making the trek yourself be sure to send me some pictures and remember the last one to Sturgis buys the beer!

More info:

My Favorite Place To Stay

Bit-O-History

Schedule Of Events For 2006

Countdown To Bike Week

Bike Week Cams

Sturguis Weather

Posted by dhite | 6 comment(s)
Filed under:

myITforum Branded News Reader For Outlook

 

Download the myITforum branded news reader from Inclue.Com. In this bundle you will find the branded readers for myITforum.com, Inc, myITforum News, myITforum Newsletters and the myITforum.com Community Forum.

 

If you use Microsoft Outlook as your E-Mail client you can use the branded myITforum news reader which integrates directly into your Outlook. It supports myITforum’s RSS 2.0, Atom 1.0 readers as well as OPML.

 

It also comes with plug-ins for Internet Explorer as well as FireFox where you can add the feeds you frequently visit easily into your Outlook from within your browser. You accomplish this by selecting the “include! Add Feed” icon from the browser toolbar and select your feed type from the dropdown arrow.

 

If you want to manually add this functionality to Outlook on any of the http://myitforum.com/cs2/blogs locate the “Syndication” leaf and right mouse click “RSS 2.0” or “Atom 1.0” and select “Copy Shortcut” and select “include!” from the Outlook toolbar and then select “Add Feed” and paste in the link that you have copied as in the examples below:

 

RSS 2.0

http://myitforum.com/cs2/blogs/dhite/rss.aspx

 

Atom 1.0

http://myitforum.com/cs2/blogs/dhite/atom.aspx

 

include! Download Link:

 

http://www.inclue.com/myinclue/friend230-1153447376

 

 

Posted by dhite | with no comments
Filed under:

Count Files In All The SMS inboxes And Send To Excel

 

Use the following Vbs script to list all of the SMS inboxes and count the number of files in them and in turn write the results to an Excel spreadsheet.

 

Note: Change SiteServerName to your site server name and change SMS_XXX to your three letter site code.

 

VBS Script:

 

sStartPath = "\\SiteServerName\SMS_XXX\inboxes\"

Set oFSO = CreateObject("Scripting.FileSystemObject")

 

Set objExcel = CreateObject("Excel.Application")

objExcel.Visible = True

objExcel.Workbooks.Add

intRow = 2

 

objExcel.Cells(1, 1).Value = "Directory"

objExcel.Cells(1, 2).Value = "Count"

 

ListFolders(sStartPath)

 

Sub ListFolders(sPath)

Set oFolder = oFSO.GetFolder(sPath)

objExcel.Cells(intRow, 1).Value = oFolder.Path

objExcel.Cells(intRow, 2).Value = oFolder.Files.Count

intRow = intRow + 1

 

For Each oFldr In oFolder.SubFolders

ListFolders oFldr.Path

Next

End Sub

 

Set sStartPath = Nothing

Set objExcel = Nothing

 

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

objExcel.Selection.Interior.ColorIndex = 19

objExcel.Selection.Font.ColorIndex = 11

objExcel.Selection.Font.Bold = True

objExcel.Cells.EntireColumn.AutoFit

 

 

Posted by dhite | 1 comment(s)
Filed under: ,

Querying The Automatic Updates Service State

 

One of the prerequisites for ITMU is that the automatic update services must be running on your client machines. If it is not ITMU will not work as expected.

 

Use the query below to find those machines that have the Automatic Updates Service (Wuauserv)  servivces state set to runing.

  

SQL Query:

 

Select 

System.Netbios_Name0 'Machine Name',

System.User_Name0 'User Name',

Services.DisplayName0 'Service Name',

Services.State0 Status,

Services.StartMode0 'Startup Type'

 

From System_Disc System

Join Services_DATA Services on System.ItemKey = Services.MachineID

 

Where Services.Name0 = 'Wuauserv'

And Services.State0 = 'Running'

 

 

To find out which machines and therefore what users are disabling the service change the line:

 

And Services.State0 = 'Running'

To:

And Services.State0 = 'Disabled'

 

Posted by dhite | with no comments

Extending Active Directory Discovery Methods Logging

 

The SMS Active Directory System, Group and User discovery method log files by default are not set to Verbose or Chatty Kathy mode and contain a bare minimum of information. This can be an annoyance especially if you are troubleshooting the processes for either of the Active discovery methods:

 

SMS AD System Discovery

AdSysDis.Log

 

SMS AD System Group Discovery

AdSysGrp.Log

 

SMS AD User Discovery

AdUsrDis.Log

 

To force the log files to spill their guts like Chatty Kathy you have to modify the corresponding registry settings under the site servers Components section of the SMS hive:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS

 

The default DWORD value is 0 (Off) and needs to be changed to 1 (On) to enable the verbose logging method. After the change has been made the next time that you initiate any of these discovery methods the log file(s) will contain more detailed information than was previously listed.

 

To set all of the active directory discovery methods to verbose logging change the following in your SMS Site Servers registry accordingly:

 

SMS_AD_SYSTEM_DISCOVERY_AGENT\Verbose Logs

 

SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT\Verbose Logs

 

SMS_AD_USER_DISCOVERY_AGENT\Verbose Logs

Posted by dhite | with no comments
Filed under:

Troubleshooting IIS Event Id’s 36 And 10004

 

When using IIS for SMS web reports or SQL Reports you may see the following errors in the system event log:

 

  • Event ID: 10004 Source: DCOM

DCOM got error "Logon failure: unknown user name or bad password." and was unable to logon .\IWAM_YourServerName in order to run the server: {1FD7A201-0823-479C-9A4B-2C6128585168}

 

  • Event ID: 36 Source: W3SVC

The server failed to load application '/LM/W3SVC/1/Root/op'. The error was 'The server process could not be started because the configured identity is incorrect. Check the username and password.'

 

IIS versions 5.0 and 6.0 includes the Synciwam.Vbs script that allows you to update the launching identity of all IIS COM+ application packages that run out-of-process.

 

The script is located in the Inetpub\AdminScripts folder and can be run using Cscript with the following command line:

 

Cscript %SystemDrive%\Inetpub\AdminScripts\Synciwam.vbs

 

Posted by dhite | with no comments
Filed under: ,

Database Snapshots For SQL Server 2005

 

SQL server 2005 has a feature called the Database Snapshot. A database snapshot is a real time copy of your SQL database in read only format. It creates this database snapshot by creating a database with reference “pointers” to the original data therefore making it read only.

 

Note:

 

This information is written to memory and as a result you need to have memory available to hold the database. If it is a very large database your memory might prevent you from creating a snapshot of your database

 

To create a database snapshot use the following syntax:

 

Create Database SnapshotName

on

(Name = LogicalFileName,

FileName = 'OsFileName')

as Snapshot of OriginalDatbaseName

 

Posted by dhite | with no comments
More Posts Next page »