April 17, 2011 – Page 2

April 17, 2011Repackaging

LANDesk Installed Adobe Patches/Updates Logs

Log File Locations: Windows XP: "C:Documents and SettingsAll UsersApplication DatavulScanvulscan.log" Windows 7: C:ProgramDatavulScanvulscan.log ——————-Patch Installation———————- Getting list of autofix patches In SendRequest: Action = SOAPAction: "http://tempuri.org/GetAutofixPatchesForGroup" Wed, 16 Jun 2010 19:13:08 SendRequest: SOAPAction: "http://tempuri.org/GetAutofixPatchesForGroup" Last status: Contacting server… Wed, 16 Jun 2010 19:13:09 Success Last status: 2 patches were found to run Last status: Done. 2 patches were found Downloading http://LANDESKSRV.TESTDOM.com/LDPatches/install_flash_player_10.1.53.64.exe LDRedirect: Checking preferred server path http://landesksource/LDPatches/install_flash_player_10.1.53.64.exe instead of http://LANDESKSRV.TESTDOM.com/LDPatches/install_flash_player_10.1.53.64.exe LDRedirect: Path http://LANDESKSRV.TESTDOM.com/LDPatches/install_flash_player_10.1.53.64.exe was redirected to http://landesksource/LDPatches/install_flash_player_10.1.53.64.exe Redirecting path <http://LANDESKSRV.TESTDOM.com/LDPatches/install_flash_player_10.1.53.64.exe> to <http://landesksource/LDPatches/install_flash_player_10.1.53.64.exe> Wed, 16 Jun 2010 19:13:13 Performing TCP connection with a timeout of -1 milliseconds Last status: Done Last […]

April 17, 2011August 12, 2014Desktop

Upgrading Symantec Anti Virus Reporting Server Component to the Latest Version

To fix the SAV Reporting Server component issue you may need to keep it updated to the latest version. Issue: SAV Reporting Console results in blank page. Investigation and Fix: After enabling debug logging, you find that SAV Reporting Server failing to connect to its DB with log#1 message. The logs uploaded by reporting agents start queuing on server. After some troubleshooting, the error transform into second error given in log#2 for which Symantec has no fix but to upgrade application to the latest version. However, the Reporting Server installer keeps on hanging forever (with log statement given in log#3) […]

April 17, 2011Windows Technologies

Disable Timeout for Active but Idle Terminal Services Sessions for Windows XP Workstations

This policy setting specifies time out for active but idle Terminal Services sessions and we had had it set to 3 hours. So, you may want to set “Sets a time limit for active but idle Terminal Services sessions” policy setting for all Windows XP workstations via group policy. This policy change will be reflected upon next group policy refresh on Windows XP workstations. However, this setting wasn’t working in XP SP2 but got into effect with SP3 deployment and causes RDP sessions to XP workstations disconnect at every 3 hours. Since RDP on Windows XP workstations supports only one […]