Ns 6 Sp3

RonKo · 01-16-2006, 09:41 AM

Has anyone installed this yet or is it too soon? If people could post their experiences with SP3 it would be much appreciated.

Thanks!

Nick · 01-16-2006, 09:57 AM

Agreed Ronko. I'll make this a sticky as well so that it doesn't get lost in the shuffle.

ChrisBlow · 01-16-2006, 02:17 PM

I just installed it yesterday and everything went quite smoothly! I definitely see a performance upgrade for the BIG reports, but I haven't played around with it much besides that. I'll give a better report once I really get to play around with it later this week.

Also...was this SP supposed to be the one with cross-browser support? I couldn't remember if they said that was SP3 or not.

jperry933 · 01-16-2006, 07:25 PM

I have read articles stating that there is a 4% rate of database corruption after installing SP3. This has been happening on various platforms, including SQL 2000 SP3 on a W2K3 Server with and without SP1. Usually resulting in being locked out of the console and then having to run repairs and/or reinstalling various solutions. The error message that shows up in the logs is "Database context was not disposed properly. Please ensure that all database context objects are properly disposed."

In our own testing, we have not been locked out of the database yet. But, we have seen that it appears to set the carbon copy and app metering configurations back to the defaults, which isn't too big of a deal if you export your xml for the settings first and then import them back in...

jharings · 01-17-2006, 04:23 PM

I was able to do an upgrade in my dev lab very successfully. One thing I'd like to point out is that I had truncated all the 'messy' tables mentioned in the NS database size link, as well as running a db defrag. This was all done BEFORE the upgrade.

It may not be necessary, however I saw my upgrade from SP2 to SP3 take less than 20 minutes, on a database that took over 3 hours to go from SP1 to SP2.

From the "other forum"

, the biggest complaint I have seen is people running VMWare. My upgrade was done on a direct console connection, on a 'regular' OS.

I did also see\hear about the 4% corruption issue, however other than the note that is was being tested\confirmed, I didn't see any real details behind that statement (error logs, screenshots, etc.).

schrameyer · 01-17-2006, 07:56 PM

I'm going to give it at least 2 weeks before I install it on my lab server. Want to see what others have to say. So far, it doesn't look to bad except for some folks running the vmware environment.

JeremyDallas · 01-17-2006, 08:40 PM

Release Notes Available Here:

Altiris Forum Topic Here:

Section 3 –

New Features in this Release

3.1 Notification Server

3.1.1 Proxy Mode Registry Setting

A new Registry setting, Proxy Mode, has been created that, when set to 0, forces the Altiris

Agent to use proxy only. If set to 1, the Altiris Agent will first try to connect directly to the

Notification Server and if it gets the WSAEHOSTUNREACH error, it will try to use the proxy.

3.1.2 Agent Locale Display feature on Altiris Agent Settings Policy

page

The new

Agent Locale Display setting on the Interaction tab in the Altiris Agent Settings

Policy page, lets you select a particular language that forces the Altiris Agent to always display

the chosen language regardless of the operating system locale.

To access this page

1. In the Altiris Console, select the

Configuration tab.

2. In the left pane, navigate to Configuration > Altiris Agent > Altiris Agent

Configuration.

3. Select an Altiris Agent Settings policy from one of the following;

•

All Desktop computers (excluding ‘Package Servers’)

•

All Package Servers

Release Notes Notification Server 6.0 SP 3 Page 7 of 57

•

All Windows Mobile

•

All Windows Servers (excluding ‘Package Servers’)

1. Click the Interaction tab.

3.1.3 Add Report feature on the Altiris Agent Installation page

Click

Select Computers on the Altiris Agent Installation page. On the Pick Resources from

Report dialog, to add custom reports to the drop-down list, click Add Report. Custom reports

can be removed by clicking the Remove Report button.

3.1.4 View Shortcut Tab Global Privilege

A new Altiris Console Privilege,

View Shortcuts Tab, has been added to the list of Global

Privileges on the Security Role Management page, on the Configuration tab.

Note

: Upon upgrade to SP3, if you are not a member of a core Altiris role, you will not

automatically see the View Shortcuts tab as access is only given to core role members.

3.1.5 /reinstall AeXNSC Command Line Argument

Previously, if you attempted to install the Altiris Agent on an existing installation of the Altiris

Agent and the versions were the same, the install would abort. A new AeXNSC Command Line

Argument has been created to enable the user to Push install the Altiris Agent on a computer

with Altiris Agent already installed. If the Altiris Agent becomes corrupted, a complete re-install

can be carried out with the same Altiris Agent version.

3.1.6 Purging Maintenance

The

Purging Maintenance page on the Configuration tab has been developed to improve

purging with the addition of the Resource Event Data Purge Settings tab. It is represented in

the Help as follows:

Purging Maintenance

This page lets you set the period for which saved reports, captured events, and managed

computers remain in the Notification Database before deletion.

To access this page

1. In the Altiris Console, select the

Configuration tab.

2. In the left pane, navigate to Configuration > Server Settings > Notification Server

Settings and select Purging Maintenance.

All saved reports and events belonging to policies older than the period you specify are

automatically purged from the database on a daily basis.

Note

: If you’re having difficulty running your reports (if they are slow), try purging your events

or set the purge of events to happen more often.

WARNING

: Purging of managed computers will cause the history of assets to be deleted (if you

have Asset Control installed). This information is very important when tracking details, such as

the cost details of assets. Enabling purging of managed computers will cause Asset data to be

lost with potential loss to financial information.

Purging Maintenance Tab

Item Description

Purge Saved Reports

Delete saved reports older

than

Purge all saved reports belonging to policies older than the period

you specify.

Purge managed

computers reporting to

Automatically remove all computers (including their inventory and

events) from the database that have not responded to the

Page 8 of 57 Notification Server 6.0 SP 3 Release Notes

Item Description

this NS, which have not

reported data for

Notification Server since the period you specified.

Also, choose to delete the computers and all associated data from the

database or retire the computers, while keeping all associated data in

the database.

Purge Now Click to immediately purge old data from the Notification Database

Apply Click to save all changes. The old data is then purged from the

Notification Database according to the schedule (if set).

Cancel Click to cancel changes.

Resource Event Data Purge Settings Tab

Computer Events

To enable purging on the entire Computer Event class, select the Data Class checkbox and

configure the Event data retention period and Max rows options, as required. Alternatively, you

can configure the data class individually by event.

By clearing any of these checkboxes, Notification Server will not enable computer event purging.

Notification Server Events

To enable purging on the entire Notification Server event class, select the Data Class checkbox

and configure the Event data retention period and Max rows options, as required. Alternatively,

you can configure the data class individually by event.

By clearing any of these checkboxes, Notification Server will not enable Notification Server event

purging.

To enable or change the purging of saved reports or events

1. In the Altiris Console, select the

Configuration tab.

2. In the left pane, navigate to Configuration > Server Settings > Notification Server

Settings and select Purging Maintenance.

3. In the content pane, click the Purging Maintenance tab.

4. Select Delete saved reports older than. Select the time period (Days, Weeks, Months, or

Years) and enter the corresponding number for your time period.

5. Select Purge managed computers reporting to this NS, which have not reported

data for. Select the time period (Days, Weeks, Months, or Years) and enter the

corresponding number for your time period.

6. In the content pane, click the Resource Event Data Purge Settings tab.

7. Configure resource event purging per data class, as required.

8. Click Purge Now on the Purging Maintenance tab.

To disable the purging of saved reports or events for this solution

1. In the Altiris Console, select the

Configuration tab.

2. In the left pane, navigate to Configuration > Server Settings > Notification Server

Settings and select Purging Maintenance.

3. In the content pane, on the Purging Maintenance tab, clear the Delete saved reports

older than checkbox.

4. Clear the Purge managed computers reporting to this NS, which have not reported

data for checkbox.

5. On the Resource Event Data Purge Settings tab, clear the Computer Events and

Notification Server Events Data Class checkboxes.

6. Click Apply.

Release Notes Notification Server 6.0 SP 3 Page 9 of 57

3.1.7 Resource Discovery link on Altiris Agent Installation page

A link has been added to the

Altiris Agent Installation page that lets you access the

Resource Discovery

page. This page lets you discover resources on the network you can install

the Altiris Agent on.

3.1.8 SMTP Port Setting

Specify an alternate port for SMTP outgoing notifications in the

E-mail Settings page of the

Setup Wizard or in the E-mail Configuration page. The default TCP port for the SMTP server is

25.

3.1.9 Disable generation of HTTP/HTTPS codebases

A setting, GenerateNSHTTPPackageCodebases, has been added to the coresettings.config file.

This setting lets you disable the generation of HTTP/HTTPS codebases for the Notification Server.

It is set to 1, by default, and HTTPS codebases are generated.

Note

: An error will be displayed in the log if the user disables both UNC and HTTP/HTTPS

codebases.

3.1.10 Enable Package Server downloading from Notification Server

only

A registry setting, PkgSvrDownloadFromNSOnly, has been added to the coresettings.config file.

It replaces the

Package Servers download packages from the Notification Server only

option on the

Status tab of the Package Servers page, which has been removed.

It is set to 0 (disabled), by default, allowing Package Servers to download from other Package

Servers and the Notification Server. Set to 1 (enabled), Package Servers will only download from

Notification Server.

Note

: If enabled before SP3 upgrade, the core setting will be set to 1 (enabled) after upgrade.

3.1.11 Global Altiris Agent Settings page

Two new tabs have been added to the Global Altiris Agent Settings page: Authentication, and

Events.

Authentication tab

This tab replaces the Package Access Credential feature, previously located on

the Package

Servers page. Specify the username and password used by the Altiris Agent to connect to a

secured resource. Also, it is the credential used by the Package Server to add file-based security

to download package files, if so configured.

Events tab

Configure individual Notification Server Event Captures, previously done on the

Advanced

Settings page. By clearing any of the checkboxes on the Notification Server Event Capture grid,

the corresponding events will no longer be sent to the Notification Server after the next Altiris

Agent setting policy request.

3.1.12 Distribution Point Credential

This feature has been added to the

Advanced Settings page on the Configuration tab. It

replaces the Package Service Access tab that was configured on the Package Servers page.

This feature is used in the creation of virtual HTTP directories when the source of packages is not

on a Notification Server. These virtual directories are called distribution points.

3.1.13 Constrained Package Servers

A new column name, Constrained, has been added to Package Server tab of the Site

Maintenance page and a checkbox has been added for each Package Server that can be enabled

or disabled.

Disabled = Unconstrained. The Package Server is allowed to download packages it requires from

the Notification Server and Package Servers within its own site.

Page 10 of 57 Notification Server 6.0 SP 3 Release Notes

Enabled = Constrained. This Package Server can’t download packages it requires from the

Notification Server, they will only download from Unconstrained Package Servers in the same

site that have the required package downloaded and ready.

For a site to function, you must have at least one unconstrained Package Server per site to

download new packages from the Notification Server. Constrained Package Servers download the

package from the unconstrained Package Server. Constraining other Package Servers in the site

will ensure one Package Server is downloading the package from the Notification Server, saving

unnecessary traffic.

If a constrained Package Server requests a package, and there are no unconstrained Package

Servers with the package ready for distribution, it won’t receive package sources to download

from. It will enter a backoff retry mode until the assigned unconstrained Package Server in the

site has downloaded the package from the Notification Server.

All instruction covering the new features is covered in Notification Server Help.

3.1.14 Site reports

To view the new Site reports navigate to

Notification Server Infrastructure > Server > Site

Reports on the Reports tab.

Site Reports Report Description

Sites without unconstrained

package servers

This report lists all sites without unconstrained package

Servers.

Subnets without unconstrained

package servers

Lists all subnets without unconstrained package Servers.

3.1.15 Manual Assignment of Package Servers to Sites

Previously, when a Package Server was assigned to a site on the

Package Server tab of the

Site Maintenance

page, it caused all subnets the Package Server was a member of, to be

assigned to the selected site.

Now, when assigning a Package Server to a site, the Package Server will only be assigned to the

selected site, not the subnet the Package Server belongs to. This means a Package Server can

be assigned to multiple sites at once.

Note:

You can assign subnets to a site on the Subnets tab of the Site Maintenance page.

To manually assign a Package Server to a site

1. Click the

Package Server tab on the Site Maintenance page.

2. Select a Package Server.

3. Click Assign to site.

4. Select the checkox of the site you want to assign the Package Server to, in the Select a

Site dialog and click OK.

The following reports identify sites and subnets in your environment without unconstrained

package servers:

•

Sites that do not have unconstrained Package Servers.

•

Subnets that do not have unconstrained Package Servers.

3.1.16 Package Server tab on the Altiris Agent Package page

A new tab, that lets you specify Package Servers to host packages, has been added to

Altiris

Agent Package page on the Configuration tab. This Package Server tab will also appear on

any Solution Agent Package page also installed on Notification Server.

Note:

Software Delivery solution does not yet contain this feature.

New Page Items

Release Notes Notification Server 6.0 SP 3 Page 11 of 57

Item Description

Assign package to Select the destination Package Server from one of the following:

All Package Servers

- Assign the package to all Package Servers.

Package Servers Individually

- Assign the package to selected

Package Servers.

Package Servers by site

- Manually assign Sites to packages from

a list of Sites configured in the Site Maintenance page. When a site is

assigned to a package all Package Servers within the selected site will

host the package.

Package Servers automatically with manual prestaging

- Sites

will be automatically assigned to packages according to the Agents

and Package Servers requirement for that package. Example: An

administrator creates a task, associates it with a package assigned to

Package Servers automatically with manual prestaging, and also

assigns a Collection to the task. Now, all members of this collection

require the package, and need to download it.

The next time Package Refresh runs, or the Update Distribution

Points button is clicked, the package is assigned to sites according to

the collection members.

So, if ClientA is a member of the collection assigned to the task, and

ClientA is a member of SiteA, then SiteA will get assigned to the

package.

When SiteA is assigned to the package it means all Package Servers

within SiteA will host the package. So, when ClientA needs to

download the package, all the Package Servers within its own site will

have already downloaded and prepared the package, or be in the

process of doing it.

This option also lets you manually assign packages to sites as

desired. So, if a site has not been automatically assigned to the

package, the user can potentially assign it to a number of other sites

manually.

3.1.17 Package Servers page

The

Package Servers Access tab has been removed from the Package Servers page. It has

been replaced by the Settings tab which contains new Security Settings features. The Package

Server Summary table on the Status tab has also been enhanced.

New Features on Status Tab

Item Description

Package Server

Summary Table

Unconstrained Package Server

- Number of unconstrained Package

Servers that download new packages from the Notification Server.

Constrained Package Servers then download the package from the

unconstrained Package Server.

New Features on Settings Tab

Item Description

Remove automatic

site assignments if

they are unused for

Remove automatic site assignments for any package that are unused for

the time specified in the drop down list box.

This feature is activated when you assign packages to

Package Servers

automatically with manual prestaging on the Package Servers tab

Page 12 of 57 Notification Server 6.0 SP 3 Release Notes

Item Description

on

the Altiris Agent Package page.

When sites are unassigned from a package, they will not be reassigned at

the next Package Refresh interval, even if there is an enabled task

associated with the package.

A package will be reassigned to the unassigned sites if an Altiris Agent in

these sites requests the package.

Published Codebase Types

Publish UNC codebase Enable Package Servers to create UNC codebases

Publish HTTP

codebase

Enable Package Servers to create HTTP codebases

Publish HTTPS

codebase

Package Servers to create HTTPS codebase.

Note

: will automatically revert back to HTTP codebase if the Package

Server does not have appropriate SSL certificate installed.

Security Settings

Allow anonymous

access to package

codebases

Enable all packages downloaded to Package Servers to have anonymous

access to the directories containing the package files. Anonymous access

will also be enabled for the directory security inside IIS for the hosted

Package Server packages.

Create the Agent

Connectivity

Credential on Package

Servers (provided the

ACC is not a domain

account)

Enable creation of the ACC (configured on the

Global Altiris Agent

Settings page > Authentication tab) on the Package Server.

Note:

This will not create the account if the Package Server is a domain

controller.

Re-enable the created local account if it has been locked out

- Allow the local account to be reactivated if it has been locked out

Create the ACC even if the Package Server is also a Domain

Controller

- Allow the ACC account to be created on all Package Servers even if it is

a Domain Controller.

3.1.18 Package Server Status reports

To view the new Package Server Status reports navigate to

Notification Server

Infrastructure > Server > Package Server Status on the Reports tab.

Package Server Status Report Report Description

Package Server password expiry Lists Package Servers with local ACC passwords due.

Package Server account creation

failure

List of Package Servers that failed to create a local ACC

account.

Package Server DC account

creation failure

List of Package Servers with local ACC accounts created on a

DC when the

Create Account option is disabled.

Package Server account locked List of Package Servers with locked out local ACC account.

Release Notes Notification Server 6.0 SP 3 Page 13 of 57

3.1.19 Notification Policies

To view the new notification policies navigate to

Server Settings > Notification Policies on

the Configuration tab.

Notification Policy Report Description

Package Server password expiry Creates a report and sends e-mail whenever there are

Package Servers with local ACC accounts with passwords

that will retire shortly.

Package Server account creation

failure

Creates a report and sends e-mail whenever Package

Servers fail to create local ACC account.

Package Server DC account

creation failure

Creates a report and sends e-mail when Package Servers

with local ACC accounts created on a DC have the

Create

Account option disabled.

Package Server account locked Creates a report and sends e-mail when Package Servers are

locked out from their local ACC account.

3.1.20 Server Performance report

A

Server Performance report has been added to Reports > Notification Server

Infrastructure > Server > Server Performance Reports. This report provides information

on Scheduled Tasks, Client Config Requests, Message Processing, and Report Execution.

3.1.21 Notification Policies for Constrained Package Servers

To view the new notification policies navigate to

Server Settings > Notification Policies on

the Configuration tab.

Notification Policy Report Description

Sites without unconstrained

Package Servers

Creates a report and sends e-mail when a site doesn’t have

an unconstrained package Server.

Subnets without unconstrained

Package Servers

Creates a report and sends e-mail when a subnet doesn’t

have an unconstrained package Server.

3.1.22 Altiris Agent Installation Option

A new feature,

Download agent package from closest Package Server, has been added to

the Altiris Agent Installation Options dialog. Select this option to download the agent

package from a local Package Server during Push Installation. This option only functions if the

closest Package Server has IIS installed and is publishing HTTP codebases for packages. UNC

codebases are not utilised.

Before the push occurs, the subnet details of the computer are discovered, and from this

information the site in which this Agent resides is determined.

Package Server selection logic

Sites defined on Notification Server

•

Package Servers from the same site as the Agent will be

returned.

•

If no ready Package Servers exist in the same site as the

Agent the Notification Server will be used.

No sites defined on Notification

Server

•

Package Servers from the same site as the Agent will be

returned

•

If no ready Package Servers exist in the same site as the

Agent the Notification Server will be used.

Page 14 of 57 Notification Server 6.0 SP 3 Release Notes

Note:

The Altiris Agent Package must be considered 'Ready' on Package Servers if they are to

be returned to the Altiris Agent. The feature does not function when performing a Pull

Installation

To access this feature

1. In the Altiris Console, select the

Configuration tab.

2. In the left pane, navigate to Configuration > Altiris Agent > Altiris Agent Rollout and

select Altiris Agent Installation.

3. Click Installation Settings.

3.1.23 Resource Association Diagram limit

The

Resource Association Diagram feature in Resource Manager has been re-designed to

show the first 20 items in an association before adding a Grouping item that contains the rest of

the associated items.

3.1.24 Security Role Management

The Altiris Console features used to manage security roles have been re-designed to help you

configure security in the Notification Server. The new

Security Role Manager console displays

information from the Notification Server database about role permissions for any given filter. The

new features also include:

•

New, open role-focussed security user interface

•

Easier role creation and modification

•

See the left pane as it appears for any given role

Previously, roles were accessed on the Security Role Management page on the Configuration tab.

This page has been removed and the Security Roles folder on the left pane has been added. It

contains the default 5 security roles, roles installed by solutions, and any roles you have created.

The Security Role Manager is accessed by the left pane or page of a selected security role as

defined below.

Security Role Manager

Console item

Description

Role: Select the role you want to configure in the

Role drop-down list.

Filter: Your choice of filter determines what items you see in the left pane and

what permissions are available in the content pane. Choose from:

•

All Collections

•

All Data Classes

•

All Items

•

All Notification Policies

•

All Resource Selector

•

All Resources

•

Tree > Configuration

•

Tree > Reports

•

Tree > Resources

•

Tree > Shortcuts

•

Tree > Tasks

Inherited Permissions View the Inherited Permissions for the role and filter selected.

Noninherited Select the permissions you want for the role and filter you have

selected. Each filter has a different set of Noninherited permissions. Use

Release Notes Notification Server 6.0 SP 3 Page 15 of 57

Security Role Manager

Console item

Description

the

Check All and Clear All options for faster configuration if you want.

Show Permissions Restrict the permissions displayed to:

•

All available permissions

•

All permissions selected

•

All permissions not selected

Advanced Click to view the Security tab, in the Properties dialog, for the item

selected in the tree. This shows permissions for all roles for the selected

item.

Note

: If you clear the Inherit the permission entries from parent

object that apply to child objects option you will break inheritance

for the item in all roles, not just the selected one.

To access Security Roles and open the Security Role Manager console

1. In the Altiris Console, select the

Configuration tab.

2. In the left pane, navigate to Configuration > Server Settings > Notification Server

Settings > Security Roles.

3. Select the desired Security Role.

4. On the selected Security Role, click Show Security Role Manager Console on the

General

tab, or right-click the Security Role in the left pane, and select Security Role

Manager in the pop-up menu.

To create a Security Role

1. In the left pane, navigate to

Configuration > Server Settings > Notification Server

Settings.

2. Right-click the Security Roles folder and select New > Security Role in the pop-up menu.

3. Enter the new role name in the pop-up dialog box.

4. On the General tab, enter a role description of the New Role page.

5. On the Membership tab, click Add new members.

6. Select users or groups for the role in the pop-up dialog and click OK.

7. On the Privileges tab select all if the privileges you want to associate with this role, and

then click Apply.

3.1.25 Notification Server Configurator

The Notification Server Configurator is a plugin that lets you modify commonly-used Notification

Server settings. Previously, these settings could only be modified manually by editing the

coresettings.config file, or changing the Windows registry settings. The Notification Server

Configurator provides a single point of access to all of these settings, showing default and

recommended values with a description of each setting. A function is also provided to help

search for a particular setting. Settings include Database Settings, Events Settings, Inventory

Forwarding and Power Management.

To install the Altiris NS Configurator

Run NSConfiguratorSetup_6_0.msi which is located at C:\Program Files\Altiris\Notification

Server\NSCAP\Bin\win32\X86\NSConfigurator.

NS Configurator page items

Page 16 of 57 Notification Server 6.0 SP 3 Release Notes

Item Description

Setting Name Core setting name.

Description Brief description of its purpose.

Type Type of setting. Example: registry or local.

Default Value Its default value at install.

Value Enter the value you want, if applicable.

Open the NS Configurator and edit a core setting

1. On the

Start menu, navigate to Programs > Altiris > Tools > NS Configurator.

2. In the left pane select the core setting you want.

3. In the Value text box enter the setting you want.

4. Click Apply to finish.

hawkeye · 01-23-2006, 03:42 PM

I just completed my upgrade and all went well. I had recently did a clean install of my NS with a new DB. I have found that these Altiris upgrades go much better with a clean install or a small DB.

I do wonder though...what happened to the much vaunted Software Virtualization Solution.

Hello Software Virtualization??

Holla!

Nick · 01-23-2006, 04:01 PM

Good to hear your SP3 upgrade went smoothly.

Last I heard about SVS was that they had to address an issue with the way a system with multiple Office applications (MS Office, Open Office, WordPerfect) would open documents.. ie which one was considered default.

I believe that has been resolved and I would expect it to be released very soon.

Take that with a grain of salt though... I also thought the Panthers were going to win yesterday as well.

lmagana · 01-23-2006, 06:41 PM

i have problems with Routing Rules, since i upgrade NS, my routing rules doesn´t work ??
Maybe change the concept ?? i have 3 queued because we have 3 different buildings, so we ruote any ticket to assigned queued, since the upgrade all email notification are sending to me. (admin).

maybe this version centralice all queued ??

Help !!

Chrissmo · 01-26-2006, 10:05 PM

Since installing NS SP3 and DS 6.5, here are the troubles

we have had (I say troubles because we use to be able to do these things prior to upgrades):

Cannot Deploy Rapid Install Packages

Cannot Image Computers

Custom settings removed

Default reports reverted to default settings (emailed daily)

PXE not working properly in all offices

Constant SQL Timeouts (was very rare before)

Can no longer use "remote control" from DS (Carbon Copy Still working)

The next day, we were locked out of DS and can not create a job that will run. 1 PXE server refuses to start the "Altiris PXE Server Service" automatically, even thought its set that way, and Services keeps failing since we applied the fix on 2006-01-15...

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7024

Date: 1/16/2006

Time: 8:21:54 PM

User: N/A

Computer: ALT001

Description:

The Altiris PXE Config Helper service terminated with service-specific error 1106 (0x452).

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7000

Date: 1/24/2006

Time: 5:19:59 PM

User: N/A

Computer: ALT001

Description:

The Altiris Deployment Server DB Management service failed to start due to the following error: The system cannot find the file specified.

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7000

Date: 1/24/2006

Time: 5:20:02 PM

User: N/A

Computer: ALT001

Description:

The Altiris eXpress Server servicefailed to start due to the following error: The system cannot find the file specified.

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7034

Date: 1/26/2006

Time: 12:01:19 PM

User: N/A

Computer: ALT001

Description:

The Altiris Agent service terminated unexpectedly. It has done this 3 time(s).

Many of these issues, I believe are Permissions issues with new Roles Security, because I (as Altiris Admin) can do many of these things other general users cannot.

Because both DS was upgraded from 6.1 to 6.5 and was brought up to 6.0.6074 (SP 3) on the same day -in a production environment too, I might add...I don't know where to start.

Keep running into issue after issue

dominique · 02-28-2006, 03:23 PM

Quote:

Originally Posted by Jeremy_Dallas

Release Notes Available Here:

Hello ,

The release notes Notification server 6.0 SP3 is oriented 5.5 to 6.0 SP3, not 6.0 SP2 to 6.0 SP3.

Any other documentation?
When I launched Altiris_NS_6_0.exe from http://www.solutionsam.com/solutions/6_0/ it start by configuring Altiris NS SP2 Hotfix #0022 then #0020 the #0019 is it back to the Future!!!
it is strange...

It went through... I did also HD SP3...

""An unexpected error has occurred. An unexpected error has occurred. parsing "Break-Fix\Printer\Not Printing" - Malformed \p{X} character escape.
Parameter name: Break-Fix\Printer\Not Printing""

Thanks,

Dom

dominique · 03-01-2006, 12:19 PM

Hello,

There is a bug in HD SP3 a the "\" could be seen as "/" sometimes by several functions. There is a workaround:Categories, Tasks, Notification Rules, etc...
http://www.altirisadmin.com/vbulleti...ead.php?t=2770

Thanks,
Dom

jperry933 · 03-06-2006, 11:06 AM

Finally upgraded our entire environment to SP3 (about 6 NSs). For the most part it went very smooth. For about 20 minutes we had an error popping up in the logs with an error ID, don't remember it off hand, but it translated out to "general access denied error". Might have been DCOM... Just know it said 4 seconds remaining for the entire 20 minutes that the errors were occuring. After that, it finished up and rebooted. The "configuring database" part took about 90 minutes. All together, from the time we clicked the update button to the time we could get back into the console was about 3 hours. On a few of the NS's we had to repair some of the solutions, the Asset Control Solution, the Mac agent, and App Metering Solution to name a few. And the Application Metering configurations were set back to defaults.

On another note, now, when my Contract and Asset mgrs try to "right click" and select resource manager for an asset, they get an access denied error on the Summaries page. I can view it with no problems as an admin. There are no errors in the logs and I have searched high and low for something that will allow me to grant them the correct perms. It worked pre-sp3. Has anyone seen this? I sent a note to our Altiris technical contact, but it might be a little while before he responds... hopefully its an easy fix. Thanks for any suggestions!

JeremyDallas · 03-06-2006, 11:12 AM

Go into the resource page, right-click on the top-level option of the summary page, and set security permissions here for each group.

jperry933 · 03-06-2006, 12:00 PM

Thanks for the replay Jeremy. That was one of the things I had tried... I added all the read rights... but it seems to only change it for that particular resource. Unless there is another way to get into the resource manager that I am overlooking. I select an asset, right click and go to resource manager, then change the permissions on the top-level summaries page.

** I figured it out. I was bouncing between two different computers when troubleshooting this and 1 was win32 and 1 was unix. I guess since each platform has different resource associations I had to change the summaries permissions for each platform. Seems to be working now.

THanks.

dbush · 03-10-2006, 10:24 AM

Helped upgrade a live environment last night with about 4500 computers attached so far. Everything went real smoothe and within an hour the server was upgraded and we were almost done with the first round of QC'ing.

Only "glitch" I've found so far I'd like to know other's take on is when doing a search for a computer in NS SP2 (ie, within a collection), it would go directly to that computer if found in the collection. In SP3 though it will find the computer, but display the top of the page # (ie, page 80/100) and then you have to scroll down to find the computer.

I only have access to one other NS SP3 right now and it does the same thing so would like to know anyone else's experiences with this.

jperry933 · 03-10-2006, 01:37 PM

After our upgrade, I had to run a repair on the Asset Control Solution because the "asset's status" drop-down for the edit-create resource page disappeared. It has been fine eversince, but for some reason, it has disappeared again. I will probably try another repair because I cannot find anything wrong with the permissions. Has anyone else seen this happening?

wchannell · 03-14-2006, 01:31 PM

I heard of an issue today that after upgrading to SP3, the PS (Package Server) agent has been upgrading before the NS Agent, causing PS's to go offline.

wchannell · 03-14-2006, 01:36 PM

Quote:

Originally Posted by jperry933

After our upgrade, I had to run a repair on the Asset Control Solution because the "asset's status" drop-down for the edit-create resource page disappeared. It has been fine eversince, but for some reason, it has disappeared again. I will probably try another repair because I cannot find anything wrong with the permissions. Has anyone else seen this happening?

What version are you currently running for NS, Server OS, SQL and DOT NET?

Also when you first installed AMS did you use the Suite install or install each solution manually?

I found that the Suite install seems to cause me nothing but grief and taking the time to install each solution works very well with no issues normally.

jperry933 · 03-14-2006, 03:26 PM

I am not at my server right now, so I am not sure of all the versions. I used the AMS suite to install everything initially. I had to run a second repair on the Asset Control Solution and everything is fine now.

schrameyer · 03-14-2006, 07:34 PM

There are a few things that NS SP3 breaks in regards to Asset Control. Asset control 6.2 is supposed to fix these. That's the only negative thing I've found with installing NS SP3. Other than some issues with Asset control, everything else has worked pretty well for me.

dominique · 03-14-2006, 07:49 PM

Hello,

Were you talking about SP4 fixing bugs of SP3 or going backward to SP2?

Thanks,
Dom

schrameyer · 03-14-2006, 07:54 PM

Altiris NS SP3 broke a couple things with asset control solution. The new asset control solution 6.2 is supposed to fix those issues. For example, in asset you can add attachments to software licenses, etc.. you have the ability to browse for what files you want to add to the license. It worked fine in asset control with NS SP2. After installing NS SP3, the browse button no longer works. NS SP3 broke it. ha!

So, the new release of asset control, 6.2 (currently in beta) is supposed to "fix the glitch"

dominique · 03-14-2006, 08:16 PM

Hello,

Thanks for the clarification, sorry I did not read well the first post as you mentionned Asset 6.2.

Dom