Hi Folks

Greetings.

This time its the similar request i discussed in my last blog, but in the Software Deployment module.    This query will help you to get the list of computers which don't have a specific software. We can call this as Software Exception Computer List :)

select Resource.NAME, Resource.DOMAIN_NETBIOS_NAME, InvComputerOS.OS_NAME, InvComputerOS.VERSION, InvComputerOS.SERVICE_PACK from ManagedComputer inner join Resource on ManagedComputer.RESOURCE_ID = Resource.RESOURCE_ID inner join InvComputerOS on Resource.RESOURCE_ID = InvComputerOS.COMPUTER_ID inner join InvComponent on InvComputerOS.COMPUTER_ID = InvComponent.COMPUTER_ID inner join InvSWInstalled on InvComponent.COMPONENT_ID = InvSWInstalled.COMPONENT_ID inner join InvSW on InvSWInstalled.SOFTWARE_ID = InvSW.SOFTWARE_ID where Resource.RESOURCE_ID Not IN (select Resource.RESOURCE_ID from ManagedComputer inner join Resource on ManagedComputer.RESOURCE_ID = Resource.RESOURCE_ID inner join InvComputerOS on Resource.RESOURCE_ID = InvComputerOS.COMPUTER_ID inner join InvComponent on InvComputerOS.COMPUTER_ID = InvComponent.COMPUTER_ID inner join InvSWInstalled on InvComponent.COMPONENT_ID = InvSWInstalled.COMPONENT_ID inner join InvSW on InvSWInstalled.SOFTWARE_ID = InvSW.SOFTWARE_ID where InvSW.SOFTWARE_NAME like "%Adobe%") group by Resource.RESOURCE_ID;

You need to replace the "%Adobe%" with the software you need to find where it is missing.

This will help in the scenarios, where you need to know the computers in which a particular software is not installed.

Cheers
Romanus

Hi Folks,

Here again for Query executor.  Trust me this is getting popular among desktop administrators for the reason it can get what they need to know about their network.

Now in to the subject, i'm going to present a query which can be used to find the computer list which was not scanned for inventory from a specific date.  This would be helpful during the internal/external auditing to check not-scanned computers and validate.  Please note, the date should be in mm/dd/yyy hh:mm:ss format.

Query to get unscanned computer list for inventory

select Resource.NAME, Resource.DOMAIN_NETBIOS_NAME, InvClientScanStatus.Last_successful_scan as LAST_SUCCESSFUL_SCAN_DATE_FORMAT  from ManagedComputer INNER JOIN Resource ON ManagedComputer.RESOURCE_ID = Resource.RESOURCE_ID Inner join invclientscanstatus on resource.resource_id = invclientscanstatus.resource_id where Last_successful_scan < DATE_TO_LONG(04/20/2009 00:00:00);

You need run this in the query executor.  Here are the instruction for those who try this for the first time.  Also, folks who don't see this option need to upgrade your build to the latest.  Contact support at desktopcentral-support@manangeengine.com

How to Execute?

1. Goto Admin  Tab -> Tools table -> click on Query Executor
2. Paste the given sql query in the text Area
3. Click on Execute Query
4. The result will be shown.
5. You have the option to export the data into CSV File for further manipulation.

cheers
Romanus

Hi Folks

Quick post on the latest request on Desktop Central forums. The requirement was on renaming the remote computer.

This functionality is not available with Desktop Central.  The Free windows tools from Desktop Central has various associated tools except remote PC rename.  So, Here is quick help with a script to rename one remote computer in the network which is under the Desktop Central Management.

How to use it?

Download and save the script.  Edit the first line "new-comp-name" value to change to your desired name.  Make sure it doesn't exceed 15 characters.

Download the Script and add it as a EXE software in Software Deployment.  Choose the reboot option while deploying the configuration.  This will rename the computer and reboot to come back with new name.

sNewName = "new-comp-name"

Set oShell = CreateObject ("WSCript.shell" )

sCCS = "HKLM\SYSTEM\CurrentControlSet\"
sTcpipParamsRegPath = sCCS & "Services\Tcpip\Parameters\"
sCompNameRegPath = sCCS & "Control\ComputerName\"

With oShell
.RegDelete sTcpipParamsRegPath & "Hostname"
.RegDelete sTcpipParamsRegPath & "NV Hostname"

.RegWrite sCompNameRegPath & "ComputerName\ComputerName", sNewName
.RegWrite sCompNameRegPath & "ActiveComputerName\ComputerName", sNewName
.RegWrite sTcpipParamsRegPath & "Hostname", sNewName
.RegWrite sTcpipParamsRegPath & "NV Hostname", sNewName
End With ' oShell

Trust this helps.  Please let me know your comments and concerns.

cheers
Romanus

Hi

This blog is about the new feature introduced in Desktop Central.

The new feature is called Query Executor (available under Admin -> Tools -> Query Executor.  This feature is supported from build 60316.  If you don't see this feature you can contact the tech support).  You can use it as SQL query executor.  Being a initial version you can send in your requirement and get the query from the Desktop Central Support Team.  Later, this can be improvised according to the need.

Query Executor can be used to generate custom reports which are not available ready-made with DC and many more what you like to generate out of DC.  For example, regarding the conficker worm, how to get the list of computers where intended patch KB 958644 (Bulletin ID : MS08-067) is installed or computers where the patch is missing.  Below given is the query to achieve the task using DC Query Executor.

select resource.name, patch.patchid, patch.bulletinid, affectedpatchstatus.status from affectedpatchstatus inner join patch on patch.patchid = affectedpatchstatus.patch_id inner join resource on resource.resource_id = affectedpatchstatus.resource_id where BULLETINID="MS08-067" and status="Available";

select resource.name, patch.patchid, patch.bulletinid, affectedpatchstatus.status from affectedpatchstatus inner join patch on patch.patchid = affectedpatchstatus.patch_id inner join resource on resource.resource_id = affectedpatchstatus.resource_id where BULLETINID="MS08-067" and status="Missing";

Hi Folk,

Great to see you all.

Tomorrow is April 1and there is a peril of Win32/Conficker worm.  Here is my findings when fiddling with this topic.

Win32/Conficker is a worm that infects other computers across a network by exploiting a vulnerability in the Windows Server service (SVCHOST.EXE). If the vulnerability is successfully exploited, it could allow remote code execution when file sharing is enabled. Depending on the specific variant, it may also spread via removable drives and by exploiting weak passwords. It disables several important system services and security products and downloads arbitrary files.

Microsoft Malware Protection Center (MMPC) has identified the following variants of Win32/Conficker:

• Worm:Win32/Conficker.A: identified by the MMPC on November 21, 2008
• Worm:Win32/Conficker.B: identified by the MMPC on December 29, 2008
• Worm:Win32/Conficker.C: identified by the MMPC on February 20, 2009*
• Worm:Win32/Conficker.D: identified by the MMPC on March 4, 2009**

More information on this can be obtained from MS site.

The following MS links talks about the solution by applying the following patch updates.

1. KB 890830
2. KB 958644

These patches are released December'08 and January'09.  Desktop Central customers would have already applied the patches.  You can ensure this from Desktop Central Server web console -> Patch Management -> Missing Patches.  Use the search feature to check the KB articles and know the status of your network.

You have the provision to install the patches from the search result of missing patches.  Patch your network using Desktop Central and get protected from conficker worm.

cheers
Romanus

Hi Folks

This topic is related to Windows Installer issues which you may experience while installing or uninstalling any MSI package. This can happen when you try to install a software application on Windows XP or Windows Server 2003, and you may receive the following error message

The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

As per the Microsoft KB article 315346, This problem may occur if the Windows Installer files that are on your hard disk are damaged or are missing. The recommended solutions for the issue are

• Reregister the Windows Installer or
• Reinstall the Windows Installer

The above solutions are described in details in the below given Microsoft link

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

In brief it does the following

Reregister the Windows Installer

msiexec /unregister and msiexec /regserver

Reinstall the Windows Installer

• Unregister Windows Installer: msiexec /unregister
• Rename the following files from the command prompt: Msi.dll, Msiexec.exe, and Msihnd.dll (to .old respective names)
• Restart Windows.
• Install the Windows Installer service again (InstMSI.exe).

The InstMSI.exe related infomartion and the file can be downloaded from given links
http://msdn.microsoft.com/en-us/library/aa369548(VS.85).aspx

http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en

While installing the Desktop Central Agents or deploying the MSI pacakges through Desktop Central you many experience this issue. Follow the steps mentioned above to overcome the problem.

cheers
Romanus

Hello Eveyone

Desktop Central supports MS Office 2003 and 2007 flavors.  What about the support for Office XP, for the those who still use it.  Here is the procedure recommended by MS, and guideline instructions to implement the same through Desktop Central.

Microsoft recommends the following unattended/silent install procedure.

Step I : Download, Extract and share the Office XP SP3 install files

1. Download the Office XP Service Pack 3 client install patch from the below given URL
   • http://download.microsoft.com/download/9/1/f/91ffc6b2-0745-470b-8dd3-1285b85db12b/OfficeXpSp3-kb832671-client-enu.exe
2. Extract the file contents and share the folder (you can extract it using Winrar or alternatively use a /C switch)
   • OfficeXpSp3-kb832671-client-enu.exe /c /t:c:\officexpsp3 is the switch the extract the files
     • hotfix.exe, ohotfix.ini, ohotfixr.dll and VSDEBUGop.msp would be the files
       
   • where /t:c:\officexpsp3 - is the location of the office XP SP3 extracted files
   • Please remember this needs to be a 'shared folder' for every client computer to access
3. In the ohotfix.ini set the following for the installation to happen in silent mode
   
   • OHotfixUILevel=q
   • MsiUILevel=q
   • RebootInQuietMode=0
   • ShowSuccessDialog=0

Step II : Copy and Share the Office XP Source Files and Create a reg file

1. Copy the entire Office XP CD contents to a shared folder
   • For example 'c:\officexp'
   • Please remember this needs to be a 'shared folder' for every client computer to access
2. In registry write the Office XP source folder location (as shown in the image)
   
   • In the given key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\9040211900063D11C8EF00054038389C\SourceList
     • '9040211900063D11C8EF00054038389C' is the Product ID of the Office XP Standard version
       
     • Create a 'Net' subkey and create a 'REG_EXPAND_SZ' key with Value name as '1' and data/expression as '\\server\officexp'
   • On the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\<Product ID>\SourceList
     • Set the 'LastUsedSource' value data as 'n;1;'\\server\officexp'
3. Now right click the SourceList (HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\<Product ID>\SourceList) and export as a reg file eg. sourcelist.reg
   
4. Copy the created reg file in the Office XP shared location i.e. 'c:\officexp\sourcelist.reg'
   

Step III : Use Software installation to deploy the Office XP SP3

1. Configure the Software package
   • In the pre-install script give the reg.exe and the exported reg file with the import option as shown below
     • reg.exe import \\server\officexp\sourecelist.reg
2. In the installation command given the oHotfix.exe file from the office XP SP3 shared folder
   • in the example \\server\officexpsp3\oHotfix.exe
   • and the same folder in advanced options - exe root path \\server\officexpsp3
3. Now deploy the Office XP SP3 installation

cheers
Romanus

Hi Folks,

I've already posted a blog on MS Office 2007 installation.  why now for 2003?  The reason was we get lot of requests still on MS Office 2003, so i'm making a brief post to address this.  Lets get into the details of Microsoft Office 2003 installation using Desktop Central.

How it works?

The Custom Installation Wizard enables you to record changes to the master installation in a Windows Installer transform (MST file) without altering the original package (MSI file).  When setup is run with both the package and the transform, Windows Installer applies the transform to the original package, and Setup uses your altered configuration to perform the installation unattended.

How to do it?

1. You need the Office Resource Kit (ORK) to customize the Office package also the actual office installation.  You can download the ORK from the below given microsoft site.

http://download.microsoft.com/download/0/e/d/0eda9ae6-f5c9-44be-98c7-ccc3016a296a/ork.exe

2. You can trigger the tool from the shown UI path.

Start -> Programs -> Microsoft Office -> Microsoft Office Tools -> Microsoft Office Resource Kit -> Custom Installation Wizard.

3. Customize your MS Office 2003 as need.  The given URL speaks about the extensive customizations of MS Office on users' computers.  (if you run the tool, its going to be pretty easy in most of the cases, if you are not sure just move ahead with next it will not cause any issues.)

http://office.microsoft.com/en-us/ork2003/HA011401941033.aspx

4. When done you will be shown with the command line to run.  Something like this

Setup.exe TRANSFORMS=UNATTENDED.MST /qp-

5. Copy and paste this command in the Desktop Central -> Software installation -> add package -> command line.  Now try with couple of computers to ensure whether your customization goes fine before you roll out to the network.

Check here for more details.

http://unattended.msfn.org/unattended.xp/view/web/50/

Cheers
romanus