Video Screencast Help

Endpoint Management Community Blog

Showing posts tagged with 7.x
Showing posts in English
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 \\...

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.

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 "%...
ianatkin | 16 Jan 2012 | 1 comment

I attended a SQL Server user group just before christmas and I found it pretty illuminating. Well worth the trip out. Altiris administrators have to wear many hats, and SQL Server knowledge is more than useful -it's critical for a smooth running Altiris setup.

I strongly advise you join a SQL User group near you. At mine they provided free pizza and we could bring in a beer from the bar downstairs.... Not that this was my primary reason for going of course....

http://sqlserverfaq.com/

You might not of course understand what they are saying,  what they are doing, or even why they are doing it... but in time you might ;-)

And making connections with SQL admins could turn out to be very useful in a time of need. And, I am of course assuming you are already a member of your local Altiris Group... right??!?

Kind Regards,
Ian./

Marcello D'Angelone | 12 Jan 2012 | 0 comments

Ghost 12.0.0.4112, shipped with Deployment Solution 7.1 and later, is capable to create / convert to VHD images.

You can convert a ".GHO" file to a ".VHD" file using ghost32.exe, ghost64.exe or the Linux version of ghost.exe.
To convert the file, run ghost with the following command line:

-clone,mode=restore,src=C:\image.gho,dst=V:\image.vhd

Now you can open Hyper-V Manager Snap-in

select New > Virtual Machine...

Open the New Virtual Machine Wizard, click Next

Allocate the amount of memory, click Next

Configure Networking, click Next

Select "Use an existing virtual disk" and Browse to the location where you stored your newly converted .VHD image