Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Database
Showing posts in English
R-Vijay | 13 Apr 2009 | 0 comments

While both deferred and immediate custom actions can run in the context of the user initiating the installation, only deferred custom actions can run elevated using the system context.

Deferred custom actions can only be sequenced between the InstallInitialize and InstallFinalize actions in execute sequence tables. Immediate custom actions, on the other hand, can be sequenced anywhere within any of the sequence tables. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the InstallExecute, InstallExecuteAgain, or InstallFinalize action is run.

Deferred custom actions cannot access the installation database. In fact, deferred custom actions have very limited access to the installation session because an installation script can be executed outside of the installation session that created it. Immediate custom actions have access to the installation...

rbrucelee1978 | 19 Mar 2009 | 0 comments

I have noticed that most of the links to sites "designed to help beginners" generally talk about how to create msi's, how to modify these packages or even how to fix some ICE errors. However, these sites do not give beginners any information on very important basic concepts such as Self Healing, Installation Sequences, how to read the logs generated on installation of the msi. These "basic" concepts can help beginners understand things like how these ICE errors occur or say in the even of a failed msi installation where to look in the package based on the information given by the verbose log file.

This site (written by John McFadyen) will provide detailed information on these concepts Windows Installer Blog.

Happy reading!! :-)

Antonp | 04 Mar 2009 | 0 comments

I had to do this prior to creating a maintainence plan for a database on my Production box.

When I first tried to create the plan I was given a message that "Agent XPs" are not enabled and that I should run sp_reconfigure.

Run this statement then you can do get on with it:

SQL Query:

sp_configure 'show advanced options', 1;
sp_configure 'Agent XPs', 1;

Cobra7 | 03 Mar 2009 | 9 comments

This is for the Windows (and WinPE) drivers for any PC that uses Intel network drivers 825XX (Such as 82567LM for example) and how to put them into WinPE.

First you will need to download the drivers from Intel, NOT Dell or HP or whatever brand you have.

You can find the site

On the search, type in the network card type (example, 82567LM). Follow the instructions, make sure you get the Vista drivers and not the ones for Windows 64.

The file you should be downloaded should be called "PROVISTA32_v13_5.exe"

Next, you can either use WinZip or WinRAR to extract the files by following this Blog:

Antonp | 13 Feb 2009 | 0 comments

After importing an AD user into the Altiris Deployment Server security the user is still unable to logon to the Deployment Server Console with his AD account and is prompted to insert a username and password to access the console or express database.

Knowing that he has been added to the DS Security, the normal AD credentials is given, but still access is denied.

Environment: Deployment Server 6.9 SP1
Database location: Seperate SQL Server
Admin rights: Local Admin Group

User's AD account is then added to the local admin group, which would work in the case where the SQL database and Deployment server is on the same box, but in this case the SQL database and Deployment server is on 2 seperate servers. So adding the his AD account to the local admin group does not make a difference.


BRING | 10 Nov 2008 | 0 comments

Standard Reports - You should be able to trust them, especially when they have to do with how complete your patching is in your environment. Normally you can check the reports (Like the "Microsoft Compliance and Vulnerability by Computer" report), and then go set up the correct tasks, and remediate the machines.

If you are like most administrators, you will know what bulletins and tasks you have enabled for distribution. So when you see them show up as vulnerable in the report it becomes very easy to be frustrated (and it could get you in trouble too!). The next thing to do is to be absolutely sure that your reports are accurate. You do this by spot-checking or auditing a few of the individual machines that are reported as vulnerable.

But what do you do when you find that the reports you trusted were wrong? The machines actually were...

haim96 | 26 Aug 2008 | 0 comments

Recently I started to get a lot of warning messages like this in the Altiris log:

Log File Name: C:\Program Files\Altiris\Notification Server\nsLogs\a.log
Priority: 2
Date: 6/25/2008 10:30:16 AM
Tick Count: 8747765
Host Name: XXXXXXX
Process: w3wp.exe (1928)
Thread ID: XXXX
Module: AltirisNativeHelper.dll
Source: Altiris.ClientTask.Web.GetClientTaskServers.LocateServersBasedOnSubnet
Description: Cannot find any TCPIP information for machine XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX

The message appears every 5 minute after collection update task.

Since there is no computer name, only a GUID. I assumed that the computer was deleted from the database (probably by maintenance task) and some leftover caused the NS to think that it still exists.

In that case, I thought, I can clean the leftovers from the DB and every thing will...

Bcomp | 04 Aug 2008 | 5 comments

How will you be able to remove old computers that were placed by resource discovery into the database? This tech tip will tell you how to do so.

The easiest way is to create a collection which shows unmanaged computers for a discovery method. Once the collection is created, review the set of computer resources, then select the needed computers, right-click, and choose Delete.

Run the following SQL query to create this collection:

USE Altiris   --Or your database name
select vc.[Guid]
, Name
, IsManaged
from vComputer vc
join Inv_AeX_AC_Discovery dis on dis.[_ResourceGuid] = vc.[Guid]
where dis.[Discovery Method] in ('DomainMembership') AND IsManaged<>'1'

Antonp | 18 Jul 2008 | 1 comment

I recently has this error when I logged onto the NS box and opened the NS console. To my surprise I wasn't greeted with the normal NS console, but instead I was faced with this:

The way I resolved this error was either to restart all the services related to the Notification Server or do a repair on the SQL database. If restarting the services didn't do the job for me, then a repair would normally do the trick.

I would like to hear from anyone who has also experienced this error and ways they resolved the problem.

marcoads | 16 Jul 2008 | 0 comments

Want to recover the Recovery Solution cluster settings in the Notification Server database? This tip will tell you the method to do so.

• Operational knowledge of the SQL Enterprise Manager required.
• Make sure no jobs are currently running on the Recovery Server and stop the Altiris Recovery Solution Server services.
• Make sure the Altiris Console is closed.
  1. On a fresh Notification Server install Recovery Solution of a correct version, Recovery Solution version can be found in Recovery Solution client registry [HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Recovery Solution Agent]Product Version =
  2. Create new Recovery Solution Cluster with same attributes as original one:
    • Cluster name, Recovery Solution database name, and database file locations must be the same...