Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Management Community Blog

Showing posts tagged with 7.x
Showing posts in English
Ludovic Ferre | 12 Jul 2012 | 1 comment

It seems to be the Package Server problem season for me [1].

Whilst trying to stabilise my customer environment so they can enjoy PXE 2.1 and OS deployment tasks I found that the two package servers have some issues accessing the deployment share... getting an access denied message (which leaves no doubt to the root cause of the error).

Package Server 2 is trying to download the drivers.manifest.txt file from Package Server 1 (fully synchronised - and freshly cleaned of .net 4.0 [1]). But all we where receiving there was an error 500 (application error).

Checking on PS1 the url provided to PS2 was effectively throwing an error, indicating that .Net could not read the web.config file in path "\\?\Deployment\...". This may look unfamiliar to most of us, but having spent a couple of hours it rang a bell immediately, as earlier attempts to synchronise PS2 threw similar errors, but locally (when the PS was attempting to copy a downloaded file to \\...

Ludovic Ferre | 12 Jul 2012 | 3 comments

In case you want to know quick the short answer is no. 

But the long answer is, well, of course you can. But you shouldn't ;-). Why you should not is because the framework makes some changes to the file handling in IIS and causes error with some Linux package that have file with no extensions.

These files are recognised as script and IIS attempts to find a loader for them, but there isn't any, given the files have no extensions. So IIS throws an error explaining that you are trying to access a script file via a static file handler, and it will not allow you to do that.

On a remote client you will see a generic 404 error message, whilst on the server itself you will get the full code 404.17.

Removing the framework 4.0 will resolve these problems, if you are encountering them. So now you know :D.

Ludovic Ferre | 02 Jul 2012 | 0 comments

It's slightly under 2 weeks since I posted my first blog entry [1] on the aila-web portal [2].

Today I am proud to announce that the portal is now at version 0.4 and brings in some visual features that will make a difference to all users: the statistics from aila are no longer displayed in text, but rather as line and bar charts.

This means you will get this:

Instead of this:

I will boldly call thiese changes a huge progress :D.

[1] {CWoC} Back at work on aila, adding a self-service portal

[2]...

KSchroeder | 27 Jun 2012 | 0 comments

So as we are working on our 7.1 migration from 6.x, we have encountered various mysteries and oddities in the way the database schema changed in 7.x (at least in 7.1, never looked very closely at 7.0).  One of these came up while we were working on recreating some filters (and reports) and we found that while Resource Manager for a particular machine shows "Notebook" for the "Chassis Package Type" in the Hardware > Chassis Inventory, the DB table Inv_HW_Chassis just has the numeric value from WMI (documented in this Technet article).  However, we ALSO found that there is a view RMV_HW_Chassis that has the "friendly" chassis type information that you would normally have to use a CASE statement to report on, along with a lot of other handy columns, like CPU "real" descriptions such as "Intel(R) Core(TM) i7...

Ludovic Ferre | 14 Jun 2012 | 0 comments

So as it appears the BaseXmlHttpcallback problem [1] is a resilient beast... I was involved in an incident this week related to the infamous problem, but on the Symantec Management Platform 7.1 SP1.

As it turned out the root cause was not the same as version 7.0, hence I'm share the information here.

How it looked in the server?

Exactly the same as on version 7.0. Red all over, with almost no room for normal service messages to show (albeit the server was fine).

How it looked on the client?

Very different indeed. First of all the "TaskManagement\Status" folder contained as lot of valid status xml files, nothing like the original 7.0 problem with empty files. Second, the Agent log file was filled with AeXNetComms and ClientTaskAgent errors related to communication.

How we solved it?

Based on the fact that the status messages were present and valid, and on the log error I went for a simple restart of the agent. This...

Pascal KOTTE | 13 Jun 2012 | 0 comments

I just correct the script gived from Gilles, to add the NS server name (to change yours).

Notice: not tested yet this one. Notice also: best to install a data partition, if available, instead a system partition !! :)

You should put, the msi file (from <\\SMPserver\NSCap\bin\Win32\X86\NS Client Installation>) and this script into NETLOGON domain folder, and add a GPO to run it at machine startup.

I would like to test if the system is a server with a data partition, or a workstation a single C drive, to deploy different path according the system type.

@echo off

set MYALTIRISPATH=%programfiles%\Altiris
if exist "%MYALTIRISPATH%\Altiris7agent.log" exit 183

rem remove all plug-in et agent altiris
if exist "%MYALTIRISPATH%\Altiris Agent\AeXNSAgent.exe" start "" /b /wait "%MYALTIRISPATH%\Altiris Agent\aexagentutil.exe" /uninstallagents /clean

rem cleanup Setup folder
if exist "%...
tgrandpre | 13 Jun 2012 | 0 comments

By: Travis Grandpre, Sr. Product Marketing Manager, Endpoint Management and Mobility Group, Symantec

Symantec is at it again. We have been named as a “Leader” in another key analyst report. This time, Symantec has been positioned in the “Leader” wave in The Forrester Wave™: Enterprise Client Management Suites, Q2 2012. This, along with our “Leader” position in the recent 2012 Gartner Magic Quadrant for Client Management Tools, further underscores Symantec’s unique global leadership in the endpoint management space.

The Forrester Wave report states that Symantec made a significant splash in this Wave, earning a position as a Leader with long-established strengths in core and extended client management functionality — particularly OS management, software management, and patch.

“...

tbenson | 21 May 2012 | 0 comments

The May 23rd Twin Cities User Group meeting is cancelled for this week.

Sorry for the late notice!

We hope to have an event in June. Please check back for further info.

stebro | 26 Apr 2012 | 0 comments

Microsoft’s Security Intelligence Report Volume 12, released earlier this week discusses the continuing challenges of the Conficker worm in enterprises. Conficker came about in later 2008 and continues to plague Windows systems despite patches for the originally exploited vulnerability being available for over 3 years. Conficker continues to spread via one of two methods: exploiting weak passwords or unpatched systems and according to Microsoft’s Tim Rains, in an article by eWeek, 92% of recent infections are due to the exploit of weak passwords.

In terms of exploiting weak passwords, the Security Intelligence Report states “This type of attack uses the credentials of the logged-in user to access local or network resources, or else attacks password-...

Ludovic Ferre | 20 Apr 2012 | 4 comments

I encountered an issue a few weeks back that was a little strange, but I didn't need to pursue it as my Windows Server 2008 VirtualBox VM Decided to die upon installing some Software Update, but yesterday a customer contacted me on the very same issue.

The problem is that you cannot install Asset Management Suite via SIM after CMS was installed. The error occurs on the InstallReadiness check named "Upgrade Required".

The readiness check is encrypted so we cannot exactly see what it is verifying and what is failing, but I have a case going to backline to check this right now.

Let's see what the error comes from, but as I answered the customer today: No, there is no incompatibility between AMS and CMS 7.1 SP2.