Video Screencast Help
Endpoint Management Community Blog
Showing posts in English
Screenbert | 05 Apr 2007 | 1 comment

When Upgrading Patch Management from 6.1 to 6.2 you may want to upgrade your NS server and then upgrade your Software Update Agents on your client machines at a later time.

This will work as long as you continue to import 6.1 PMImport updates instead 6.2 PMImport updates.

In order to do this, change your Patch Management configuration under Configuration -> Solution Settings ->Software Management ->Patch Management ->Server Settings ->Import Microsoft Software Management Resource.

Make note of the current URL and save it somewhere. Then put the old 6.1 URL in

http://www.solutionsam.com/imports/6_1/patch/microsoft/pmimport.cab 

When you upgrade your clients, go ahead and change this again, putting in the 6.2 PMimport URL and you'll be set to go!

BRING | 04 Apr 2007 | 4 comments

Some users have found that their Notification Server is taking a long time for console refresh and access. Learn how to speed it up here.

While there are certainly many reasons behind this, one simple reason is documented in a knowledge base article titled:

"How do I Turn off AEX SWD Status Summary Events?"

This KB article gives one option to reduce one area of processing load on the NS. There are some limited reporting tradeoffs here,
but for the most part, this is a setting that can easily be adjusted.

See KB 32172 for the full details.

BRING | 03 Apr 2007 | 3 comments

When upgrading our Altiris Agent environment, such as deploying a roll-up or service pack, there are always a few straggler machines that seem to get 'stuck', and don't complete the agent upgrade task.

The tip found in a knowledgebase article can be the key to giving those machines a 'boot', so to speak..

Check out the KB Article below, entitled:

"After NS Core R3 Upgrade, some agents would not upgrade." - KB 33865

It can be found at:

https://kb.altiris.com/article.asp?article=33865&p=1

Admin | 02 Apr 2007 | 0 comments

This podcast supports the Altiris-sponsored The Definitive Guide® to Vista Migration eBook. Plug in to get answers to the following questions:

- How to understand the needs of your technical teams
- How to design systems that ensures your teams will properly graduate testing from one level to another
- How to make the most of virtual technologies when building the migration lab

Podcast 3: Build the Perfect Migration Lab, by Danielle and Nelson Ruest, is available here.

GarethStewart | 02 Apr 2007 | 3 comments

The common practice inside most enterprise environments that I've seen are to create one large MSI for any size application. Here's an easy way to make those packages install faster.

If you compile your applications with the "Cabs Outside" option, your packages will install 50% quicker compared to "Cabs Inside".

To do this for all packages, just go into the Windows Installer Editor template you're using and go to Media and change the option to "Cabs Outside".

Screenbert | 02 Apr 2007 | 0 comments

If you ever need to execute a method against different DS servers when using the Web service in the ASDK use this code to switch between servers. This is useful when you need to find out which DS server a computer is located on and then execute a method against that computer.

ComputerManagementService computerManagement = new ComputerManagementService();
String strTargetServer = "SERVER.DOMAIN.COM";
computerManagement.Url = string.Format( "http://{0}/Altiris/ASDK.NS/ItemManagementService.asmx", strTargetServer);
CredentialCache cache = new CredentialCache();
cache.Add( new Uri(itemMS.Url), "Negotiate", new NetworkCredential( username, password, domain ) );
computerManagement.Credentials = cache;

Just change the strTargetServer to the next server. You could wrap this code in your own method to loop through all your servers and return the proper server that has the computer you are looking for.

Admin | 30 Mar 2007 | 2 comments

It's costing more and more to lose data, according to a survey of companies that recently experienced customer data loss. Can you afford $182 for each name that seeps through your security? Get the scoop on the report from SearchSecurity.com here.

Here's an excerpt:

Data breaches cost companies an average of $182 per compromised record, a 31% increase over 2005, according to the survey conducted by the Elk Rapids, Mich.-based Ponemon Institute.

Ponemon studied 31 companies that experienced a data breach. The total costs for each loss ranged from less than $1 million to more than $22 million, according to the 2006 findings.

Read the complete report here.

trb48 | 29 Mar 2007 | 21 comments

I was surfing the web today and I ran across this article: "The Lazy Guide to Installing Knoppix on a USB Key". This could the the solution to everyone's WinPE licensing woes. If we can install Knoppix on a USB key, and use it to deploy images life would be great. Why? Because Knoppix is FREE!

There are many benefits of using a USB key. The most obvious to me is that you can keep your data from session to session. Another is you can install software (i.e. all the files you need to deploy an image). Hopefully, the networking drivers will already be packaged in Knoppix.

trb48 | 29 Mar 2007 | 2 comments

I was just reading Universal Silent Switch Finder posted by duijsterj. I really liked the tool because I have spent a lot of time creating what I call Silent Install Packages (and the tool that he mentioned will save me a ton of time in the future).

Basically, if I have to install something I will find out all of the switches I need to use to make it install itself. Here are some resources that I have found that makes creating silent install packages much easier:

Screenbert | 29 Mar 2007 | 5 comments

There is a KB article available for "Common problems for very large environments" and is #26878. Particularly interesting is the last item under NS relating to IIS and .NET's debug mode for asp pages.

Quite a few solutions that are out right now that mistakenly have Debug enabled. This causes additional load on IIS / NS server.

Turning the debugging off on the asp.net pages should help in these three areas according to the KB article.

  1. The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)
    This can be seen in the initial viewing of each NS console page
  2. Code can execute slower (since some additional debug paths are enabled)
  3. Much more memory is used within the application at runtime
    This is of particular importance on NS servers with 2GB of...