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,

Happy New Year to everyone!

wow! what a way to finish a year.  Thanks to all who encouraged and helped us to be here.

Yes, it was a year of challenges.  Desktop Central has grown a lot in all aspects, Number of Customers, Revenue, Product Features, Supported infrastructures, scalability, performance, usability etc., and also it is worth to mention that the evaluators/customers have started pouring requirements and suggestions directly.  This really is a sign of path to sustainable development.

Desktop Central as product has faced lot of challenges and marked different achievements, below given are the few important milestones in the year 2008 from the features point of view.

• Support for Microsoft Office patches.
• Enhancements on Power management.
  
• Support for VISTA Operating System.
• 64-Bit OS Support for Inventory, Patch Management, Software Deployment and Remote control.
• Introduced Re-Branding Option
• Windows 2008 operating system is supported.
• Action Log Viewer is enhanced to scale User Auditing.
• Desktop Central Agent runs on its own service. (No depends on GPO)
• Help Desk ticketing module introduced.
• Enhancement on Inventory (Software Grouping, Licensing modules)
• Mailing the AD Reports introduced
• DB Migration to remote computer is supported
• Support for managing computers in WAN/Remote Offices included
• Remote Management Tools enhanced.

Apart from the list of features mentioned, the DC core Engine and the agent has been fine tuned to scale to different heights.  Due to this we have started witnessing more enterprise customers with large number of computers.   We get more downloads happening and the support witnesses.  This is really a driving force.

On the other hand, the Free Windows Tools from Desktop Central is also creating sensation.  Now it has 10 tools integrated in its pallette.  It is a great complementary product for Desktop Central.  This tool also gets more feedback and suggestion from the network administrators. More plans ahead for this.

To recap, it was a splendid year packed with enthusiasm and challenges which kept us in a right rhythm, busy with new features, releases and customer support.

Hey 2008, we really loved you, adieu!. And we are ready to take the new 2009 excitement pack.

Once again, Thanks to all who encouraged and helped us to be here.

Cheers
Romanus.

Hi Folks

Here is a critical patch release for Internet Explorer.  Below given is the description of the issue as described by secunia security advisory.

Description : A vulnerability has been discovered in Internet Explorer, which can be exploited by malicious people to disclose potentially sensitive information.  The vulnerability is caused due to an error in the handling of redirections for URLs with the "mhtml:" URI handler. This can be exploited to access documents served from another web site.

Technical Explanation from MS (Bulletin MS08-078 - Critical)

A remote code execution vulnerability exists as an invalid pointer reference in the data binding function of Internet Explorer. When data binding is enabled (which is the default state), it is possible under certain conditions for an object to be released without updating the array length, leaving the potential to access the deleted object's memory space. This can cause Internet Explorer to exit unexpectedly, in a state that is exploitable.

An attacker could exploit the vulnerability by constructing a specially crafted Web page. When a user views the Web page, the vulnerability could allow remote code execution. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user.

Microsoft has released the fix for the reported IE Security hole.  You can deploy these latest critical patches to your network using Desktop Central Patch Management.

http://www.microsoft.com/technet/security/bulletin/ms08-078.mspx

Above mentioned URL has the information about the fixes and other details.  Desktop Central supports the deployment of all the 18 patches.  You can update you vulnerability Data Base through DC and do a scan to deploy this critical patch.  Since its a Critical patch, lets patch it immediately and with ease through DC.

Merry Christmas.

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