Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with 7.x
Showing posts in English
Pascal KOTTE | 03 Oct 2012 | 4 comments

Did you already angry because not able to export or copy/paste (text) the content of a filter ? As we were able with NS6 crying

With a report, we still are not able to copy/paste directly into Excel no It is one our feature request to Symantec enlightened thanks to vote those:

ianatkin | 20 Sep 2012 | 0 comments

It's just been brought to my attention that Brian Madden yesterday posted this very interesting blog,

http://www.brianmadden.com/blogs/brianmadden/archive/2012/09/19/here-s-how-symantec-can-dominate-the-quot-new-quot-desktop-fingers-crossed-they-don-t-screw-it-up-again.aspx

Interesting to see how others on the outside see the Symantec's plays in desktop management space. 

jasonfo | 18 Sep 2012 | 0 comments

If you have ever needed to create a report but dont know what table you are looking for this might help you out. In my case I had to find something that had the "Publisher".

 To look for columns in view...

USE
Symantec_CMDB
SELECT
V.name AS View_name,
SCHEMA_NAME(schema_id) AS schema_name,
c.name AS column_name
FROM sys.views AS v
INNER JOIN sys.columns c ON v.OBJECT_ID = c.OBJECT_ID
WHERE c.name LIKE '%Publisher%'
ORDER BY schema_name, View_name;

To look for columns in tables...

USE
Symantec_CMDB
SELECT t.name AS table_name,
SCHEMA_NAME(schema_id) AS schema_name,
c.name AS column_name
FROM sys.tables AS t
INNER JOIN sys.columns c ON t.OBJECT_ID...

ianatkin | 21 Aug 2012 | 8 comments

Just spent the last few days trying to figure out why my Dell Latitude E6430 wasn't responding on the Super-Speed USB ports in Windows XP. It came in with BIOS rev A02 and defied valiant attemtps to get a response in Windows from these ports. USB mice, Keyboards and Flash drives all failed to get a response from the port.

After a support call with Dell, I upgraded to A03 (although no release notes on the A03 update to say what this update resolves). Still no joy. Left it alone for three days and this morning plugged in a USB Flash drive.And magically it all worked. Hmm.... perhaps I didn't reboot enough after upgrading to A03??

So I got hold of the A02 BIOS and downgraded. USB ports still fine. WHAT?!?!? Nothing I can do now can return the machine to it's previous state of buggered USB 3.

Go figure huh? Time to blame it all on comic rays and move on. The alternative is of course to accept that I'm going mad. Naturally, that I...

ianatkin | 08 Aug 2012 | 0 comments

As I keep forgetting where the Dell driver cabs are, I thought that I should document it somewhere.... ;-)

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx

For those of you out there that download drivers by going through the Dell support website, you'll find these CABs a dream. All the drivers for your model in one place. I generally just do an inf search through the folder structure, looking for the Device ID I need.

Ludovic Ferre | 28 Jul 2012 | 0 comments

This week I had a remote session to help a customer troubleshoot SQL Connectigvity issues. This was a ressurgence of an hold issue, namely the Client Message Dispatcher service would throw regular errors indicating that the Sql Connection is not available or was closed.

The customer had migrated from a local SQL instance to a remote SQL Server (which had multiple benefits, including the switch to a 64-bit platform there) and the problem was apparantly resolved. However it came back this week, so we took a fresh look at it.

First we needed to instrument the Client Message Dispatcher, to acertain whether the issue was really impacting or not. If you are a regular reader of my blog post you will know what my standard answer to these kind of issues is: Altiris Profiler.

Only that the profiler would throw an exception on invokation, of type Cryptographic ... We solved that one issue thanks to Google and the Symantec KB, by simply crafting a new Sql Connection string...

Ludovic Ferre | 23 Jul 2012 | 2 comments

I have struggle a bit with my preferred tool to understand where the profiling data is stored these days, as it has changed quite a bit from the initial release of the tool in version 6.0 SP3 (this dates by quite a bit now).

It started a few month ago when one of my customer had some issues. We noticed that clearing the profiler was very slow. Going at data rates of just a MiB per second.

I was trying to locate the buffer files, as the profiler versions early from 7.1 used to store the data in a zero-impact buffer file. But this was not yielding any results. I could see from the Windows folder some temp files being written but not much else.

It continued with another customer last week, and today whilst I was opening a 16GiB buffer file it all came clear. I started by cleaning up a local drive to have enough space to old the file and do a local import. After copying the full file at a rate of 375 Mbps (still it took ~10 minutes) I thought I had done most of the...

Ludovic Ferre | 18 Jul 2012 | 0 comments

I have collected Symantec.pl.xml files since the beta in February 2009 and have a repository of 2.5 GiB of XML here at home. I am not devoting much time to the task to be completely honnest, as a shell script take care of verifying if a new file is available every 5 minutes.

I have also crafted a few (Linux) utilities to get some information out of the xml files. The first one was just a file cleaner that hanlded the task of clearing the pl.xml from any localisation. I never made much use of it, however it was of great help when I discussed with the product team improvments that later came to the prioduct listing and how the Symantec Install Manager handles it (first a compressed version of the file and then a langaue agnostic version). The second utility is still in use scrapes package related data from the xml, and crafts a mirror tree of the SolutionSam site. It even has the feature to copy MSI files to the correct location if they are in the same folder as the tool....

Ludovic Ferre | 13 Jul 2012 | 3 comments

If you have followed the Package Server saga [1][2] on my Connect Blog you will be happy to hear that we got it all working today, but not without a last twist, that takes us to this blog post subject.

In this customer the SMP and Site Servers do not have access to the Internet. This is a not a real problem for our products however it (the lack of Internet access) has one major impact related to a security feature of the Microsoft .Net framework that I will resume in three points:

Assembly signing, assembly loading and CRL.

To ensure that .Net code is globally and securely accessible on a workstation (i.e. for an assembly/dll to be stored in the Global Assembly Cache - also known as the GAC) Microsoft enforces assembly signing. This means the assemblies are protected against tampering.

Now comes assembly loading. In our products we use code that is shared amongst many part of the product. This code leaves in DLL that...

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 \\...