Alot of subtle changes being made as we move forward. A few products are being piloted and some issues being sorted out.

Pilots:

PC Anywhere is being rolled out today or tomorrow. This will give us a look at how stable the product is compared to Remote Desktop in the DS 6.9 products(Which was a wonderfully reliable product except on multi monitors). Working ok in the lab so far.

Do What?

The Software manager. This is one ridiculous product. it's a library of your installer files(Which means it keep s acopy of everything to do not a whole lot with, wasting disc space?) The software you import in here and add command lines in the package tab can be replicated to the Package servers, but some how this storage space isn't available as a Package server source? Also if we went through the time to import the command lines for the product, how come you still have to go back in and set the newly imported product as Manager? Why would anyone go through the...

I just finished a remote session with a customer that found a computer from the database that is not sending data back.

I had received the log files yesterday and the log viewer was all red and blue. Upon inspection it was clear that the agent COM components are not working (not registered or unregistered), so no basic inventory, client session management or sub-agents could perform their normal tasks.

Still the agent was getting it's policy file from the server, but not being able to do anything with the given policy (given its state).

We checked the computer Windows logs and found nothing interesting in there, so we crafted a SQL query to detect other computers with similar issues:

select 
       distinct(s.ResourceGuid),
       i.Name, MAX(_eventtime) 'Last config request',
       MAX(s.ModifiedDate) 'Last Basic Inventory',
       MAX(s.createdDate) 'First inventory',
       DATEDIFF(d, max(s.modifiedDate),
       MAX(c....

Recently, a Servicedesk 7.1 Sp1 user encountered a very perplexing problem.  When resolving incidents, the amount of time required for the process viewer to refresh and show that the incident is resolved or closed is normally a short time (2-3 mins).  However, this users system was not showing the incident resolution until anywhere from 14 - 40 minutes after the Close Incident task was completed.

Thru SQL profiler trace, and Info level log review, it was discovered that this issue surrounded incident escalations.  Further analysis showed that in the SD.IncidentManagement project, in the Initial Diagnosis Model, under the Event Configuration tab of  the Initial Diagnosis dialog workflow component, in the Escalation Configuration section,  there was an escalation named “Scheduled”.  It has a decision model with 40 elements in it, and was running every 10 minutes.  It was designed to be sent out for a scheduled re-opening of...

With the new year upon us, it’s time for Arellia’s 2012 analysis of Adobe Security Bulletins and those with privilege exploits. As a refresher from the Introduction on Privilege Exploitation, privilege exploitation is where the malicious software takes advantage of the rights of the logged in user to change the configuration of the local computer.  Breakdown of Adobe Bulletins: