App Center v4.2 Migration guide

Migration to Symantec App Center 4.2 involves adding new servers that support RHEL/CentOS 6.4 and adding an MDM Core database to the existing App Center database. The migration will involve some down time to current production servers. A first version of a migration guide has now been published to Symwise. This document describes what you'll need to know about migrating to Symantec App Center v4.2. The document can be found here: http://www.symantec.com/docs/DOC6841.

Physical \ Virtual Computer issue

More info on this issue can be found here

ITMS 7.1 SP2 MP1 Rollup Version 7 Release Notes

A nice recap of all fixes in all rollup Version can be found here

Symantec Endpoint Protection 12.1.4 is now available

On November 5, 2013, Symantec released Symantec Endpoint Protection 12.1.4. You can download this version from Symantec FileConnect or the Business Critical Services Web site.   
   
This version contains a number of new features, including support for Windows 8.1 and Mac OS X 10.9, a suite of new features for managing Mac clients, and an improved mechanism for reporting priority events as they happen, as well as fixes for customer-reported issues.  Symantec recommends this upgrade for all customers, especially those who manage Mac clients, use Windows 8.1, or require one of the fixes that are included in this release.   
   
For more information about this release, read the updated product documentation in the Related Articles section.

Related Articles

• DOC6838   Symantec™ Endpoint Protection, Symantec Endpoint Protection Small Business Edition, and Symantec Network Access Control 12.1.4 Release Notes

• TECH212063   System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1.4

• TECH211972   New fixes and features in Symantec Endpoint Protection 12.1.4

• TECH211821   Upgrading or migrating to Symantec Endpoint Protection 12.1.4 (RU4)

• HOWTO92146   Overview for Symantec Endpoint Protection 12.1.4 for Mac

Supportability Statement for Microsoft Windows Embedded

A PDF can be found here

SQL Maintenance script for the Symantec Management Platform database

There is a script available to create a Maintenance task on SQL Server here

ServiceDesk 7.5 SP1 Release Notes

Can be found here

Workflow Template - Zero Day Patch Video

Can be found here

What is new in SQL2012

A lot....even to much to mention in a blog so here you can find out more

SQL Version builds

	RTM (Gold, no SP)	SP1	SP2	SP3	SP4
SQL Server 2014      codename Hekaton
SQL Server 2012      codename Denali	11.00.2100.60	11.00.3000
SQL Server 2008 R2      codename Kilimanjaro	10.50.1600.1	10.50.2500	10.50.4000
SQL Server 2008      codename Katmai	10.00.1600.22	10.00.2531	10.00.4000	10.00.5500
SQL Server 2005      codename Yukon	9.00.1399.06	9.00.2047	9.00.3042	9.00.4035	9.00.5000
SQL Server 2000      codename Shiloh	8.00.194	8.00.384	8.00.532	8.00.760	8.00.2039
SQL Server 7.0      codename Sphinx	7.00.623	7.00.699	7.00.842	7.00.961	7.00.1063

Altiris Licensing - Technical FAQ

How does Altiris licensing work for Notification Server based products?

• How a license is consumed.
• What happens when the license count is exceeded.
• What happens when a time limited (demo/install) license expires.
• What happens when the Automatic Upgrade Protection (AUP) expires.
• How to recover a solution license (retirement vs. deletion).
• Anomalies in expected functionality.

More info about this topic can be found here

How to prepare a workstation for imaging that includes the SMP/NS Agent (Updated October 2013)

Problem

How can I image a computer with the Altiris Agent on it? What is needed to prepare the NS Agent when distributed as part of an image?

 

The Altiris Agent has a unique GUID for each workstation. If done incorrectly, when a new workstation is started with the same GUID as another, Notification Server will begin to manage it as if it is the same system as the other. Inventory from the multiple computers keeps over-writing each other, so systems "seem" to disappear from the NS/SMP console.  MANY solutions are impacted by this.

 

Additionally, Microsoft OS's include a SID or Security Identifier which is unique, and is how Microsoft keeps systems separate in Active Directory.  Like the GUID, if this is duplicated on the network, it causes significant problems in AD and we frequently have to refer customers to Microsoft for multiple days of cleaning up AD.

 

Resolution

Depending on the version or product you're using, there are several potential options.
Using GSS

Ghost Solution Suite has no built-in mechanism for removing the GUID's from NS.  That said, if you have NS7, you most likely have DS7 and should follow the steps for imaging using DS7.

 

However, if you do not have DS7 (or do not intend on using it) then you can either remove the Altiris Agent prior to capturing the image (recommended) or manually remove the GUID from the Agent.  The GUID is in 3 locations in the registry:

 

1. HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\MachineGUID
2. HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\NS Client\MachineGUID
3. HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent\MachineGUID

It should be noted however that the agent must be stopped for this to work.  As soon as the agent re-starts, those registry keys will be repopulated!  So, to do this, you should stop the agent service (leave it set to automatic), remove these registry keys, and immediately follow standard procedures in GSS to capture the image without restarting the system in production OR restarting the service.

Using DS 6.5/6.8/6.9
Any of the supported versions of DS 6.x will remove the GUID from the NS/SMP agent if capturing using the supported methods.  The capture image task takes care of this for you by first removing the GUID from the agent and then running Microsoft's Sysprep tool, and then rebooting and capturing the image while in this state.

Using DS 7.x
DS 7.x takes care of this when you run the Prepare for Image Capture task (which is run prior to capturing the image itself).  This is the only supported method of capturing a disk image (as apposed to a backup image). The Prepare for Image Capture task takes care of this for you by first removing the GUID from the agent and then running Microsoft's Sysprep tool  Unlike DS 6.9, you then need to run the Capture Image task separately (before a reboot to production), but the net effect is the same.

Doing things manually (Unsupported)
There are those who insist on running Sysprep manually and only using our engine/tools (Ghost and RDeploy) to capture and deploy the images.
At least one reason for this is that there is a Microsoft Technet article that indicates that the "appropriate" way to modify the default profile is to run Sysprep in Audit mode and then modify the default profile prior to image capture.  Our built-in processes do not support this.  The default profile can be modified in several other ways that are supported by our processes, but we acknowledge that those methods are not "as complete" as the one indicated by Microsoft.  99% of our customers have been satisfied with the other methods of modifying the default profile and we highly recommend trying our method first.  If you are then still not satisfied and insist on doing things this way, you should consider a few things:

• IF the agent is included then the 3 registry keys indicated under the GSS method must be removed.
• The Unattend.xml MUST be correctly managed by yourself.  We continually see problems with this method in the XML files where there are issues with architecture and custom commands.  Custom Unattend.XML files are not supported by Symantec, though support offers a best-effort level to help you find / identify problems with it.

NOTE:  If you are using DS 7.x and attempting this method, the Agent should be included and the keys removed manually.  This is a very awkward and again unsupported way of doing things, but in order to synchronize with post-imaging processes, we recognize the need to have the agent installed.  You could actually install the agent post imaging, or follow the KB on including the installer into the Unattend file, both of which would work, but both of which will delay any post-image processes / tasks you may have included in the job.  We recognize this as a viable process, but do not recommend it or support it, other than in a best-effort mode.

Not using Sysprep (Very Bad & Unsupported)
This is both not supported by us and not supported by Microsoft.  Some have found a single article published once-upon-a-time by a Microsoft employee who claims that Sysprep is not needed.  This is incorrect!  Every customer we have found who has done this has required several DAYS of support from Microsoft to clean up their directory.  We will send you to Microsoft when you run into problems and we will not be able to help you with your Active Directory (we can help with duplicate GUIDS, but be warned, it can be messy).  For imaging to work in ANY of our environments, Sysprep MUST be run in some method or manner.
The only exception to this is if you are taking a backup image of a single system and restoring ONLY to that system.  As soon as an image is deployed to more than one system without Sysprep having been run first, it is in an unsupported state.

ITMS 7.5 (Orion) Release of Workflow and Existing Servicedesk Installations

With the release of ITMS 7.5 (Orion), a new version of Workflow is now available. Can I install this version on my existing Servicedesk server?  

Answer: 

No! This is a standalone version of Workflow that is NOT compatible with any version of Servicedesk that is
currently in production. You will break your Servicedesk installation by installing the Orion version of Workflow on your Servicedesk 7.5 server. You should wait until the upcoming 7.5 Sp1 version of Servicedesk releases (scheduled for the first part of November 2013), and update your Servicedesk installation with the revised Workflow and Servicedesk versions that are included as a part of that release.

Quick reference to the HOWTO doc for ITMS 75

These can be found Here

Support Matrix ITMS (6, 7, 71, 7.5)

Can be found here

KNOWN ISSUE: Upgrade to ITMS 7.5: Some tables in DB have different definition form tables in case of clean setup - missing indexes

This issue has been reported to the Symantec Development team. A fix will be available in a later release (Post ITMS 7.5 release). The following is provided as a workaround. Basically run the following queries on your SQL Database to recreate the missing indexes: --Index for ResourceTargetContainerChanges IF NOT EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo]. [ResourceTargetContainerChanges]') AND name = N'IX_ResourceTargetContainerChanges') CREATE INDEX [IX_ResourceTargetContainerChanges] ON [dbo]. [ResourceTargetContainerChanges] ( ResourceGuid ) --Index for ItemPresentation IF NOT EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID (N'[IDX_ItemPresentation]') AND name = N'IDX_ItemPresentation') CREATE INDEX [IDX_ItemPresentation] ON [dbo].[ItemPresentation] ( BaseGuid ) -- Index for Evt_NS_Item_Management IF NOT EXISTS (SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo]. [Evt_NS_Item_Management]') AND name = N'IDX_DC_457b321d-26eb-449d-996c- 5aff16a391ec_ItemGuid') CREATE INDEX [IDX_DC_457b321d-26eb-449d-996c-5aff16a391ec_ItemGuid] ON [dbo].[Evt_NS_Item_Management] ( ItemGuid )

How to increase Queue processing performance in SMP 7.5

Can be found here

How to use the 'upgradeif' setting for CoreSettings.config

Can be found here

ITMS 7.5 installation, upgrade, and migration prerequisites

Can be found here

pcAnywhere solution filters are not properly populated in the SMP 7.5

Solution an fix can be found here

EPM 7.5 (Altiris 7.5) Landing Page

Documentation landing page can be found here

VMware Workstation 8 new features detailed

More detail can be found here

IT Management Suite 7.1 SP2 (Valencia)Documentation

All documentation can be found here

How the Retired status for a computer works

Article URL http://www.symantec.com/docs/HOWTO52993

When a computer's status is changed to Retired (which is a Notification Server core status type), several functions occur to this computer:

• The Retired status does not uninstall agents from the computer.
• If the Inventory Solution agent is installed on the computer, it will release one license for Inventory Solution.
• When the Clean Inventory task runs, software licenses are then cleaned up.
• If this is for Symantec Management Platform 7.x, if an agent is still installed on the computer, when basic inventory checks in, the status of the computer will automatically change to Active. Note: In SQL, the computer's IsManaged field is set to 1 when its status is Active (managed). If the  status is changed to Retired (no longer managed), IsManaged is set then to 0. This will revert back to 1 once the agent checks back in with inventory, however

Improving IIS and Notification Server response times by disabling debug mode

 

How can I disable debug mode compiling of ASP.NET code on my Notification Server 6.x and Symantec Management Platform 7.0 & 7.1?

Article URL http://www.symantec.com/docs/HOWTO6940

About how application metering summary is sent

The metering summary data is sent to the Configuration Management Database (CMDB) in batches. You can also specify to send event data in batches when you create an application monitor policy.

An application metering usage summary is sent for all application metering policies for which the applications are marked as allowed. The summary is sent daily by default.

See About application summary data.

See Configuring application metering data.

To prevent an overload to the system when this data is sent, the data is not all sent at the same time. The data is randomly sent over an interval of time. A value in the HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Application Metering registry key on each client computer determines the length of the interval. The name of the value is Fuzzy Factor and its default value is 10.

This value specifies the time interval when the data can be sent as a percentage of the total batch creation time. For example, the data is sent to the CMDB every seven days (168 hours) and the Fuzzy Factor value is 10. Then the length of the interval is 10% of seven days or about 17 hours. Half of this interval precedes the specified send time and half of it follows. Thus the time interval in which the data is sent would start after about 159 hours and end after 177 hours.

To change the length of this time interval, you must change the value of this registry key on each client computer. Any registry changes should be done with caution.

Removing Dell branding

Removing Dell branding  after DMC install on NS 7.0 was done by this query:

UPDATE Item SET ModifiedDate = ( select getdate() )
WHERE Guid = (    SELECT Item.Guid
                        FROM Item
                        Join ItemClass ON Item.Guid = ItemClass.Guid
                        WHERE ItemClass.ClassGuid = '1f768417-511a-4c22-afbc-4a66720f793a'
                        and Item.Name like 'Default%' )

Dell Solutions and the Symantec Management Console

Article URL http://www.symantec.com/docs/HOWTO59488

How do I configure Patch Management 7.1 SP1 to operate without internet connection.

http://www.symantec.com/business/support/index?page=content&id=HOWTO59024

How to Turn Off/On a Policy on the SMP database

If for some reason you can't turn off/on a policy (the Symantec Management Agent Installation policy) or you can't access the SMP Console or load the actual policy page, how can you turn on/off a policy directly on the database?

To disable (turn off) a policy, run the following query:

update i
set State = REPLACE(cast(State as nvarchar(max)), '<enabled>True</enabled>', '<enabled>False</enabled>')
from Item i
where Guid = '124D0571-4725-466C-8F43-998160D3CFF2'  --Place the Policy GUID in this area. As an example we are using the GUID for the Symantec Management Agent Installation policy

To turn On (enable) a policy, change the entry [ '<enabled>False</enabled>', '<enabled>True</enabled>' ] on the query above.

Article URL http://www.symantec.com/docs/HOWTO59606

DS 6.9 - What is different between using the AClient and the DAgent when doing remote control?

Ref : http://www.symantec.com/business/support/index?page=content&id=HOWTO59807

There are some differences between using DAgent and AClient when using Deployment Solution 6.9's Remote Control feature.

WIth the AClient, you are allowed to connect to a client computer when no-one is logged in. With the DAgent, someone must be logged in at the client computer before DS can control that computer. This means that if a user logs out of a Remote Control session using DAgent, the connection will drop. This difference is designed to improve security of Remote Control. You can try a different Remote Control tool Refer to the document: How to setup VNC to remote clients in Deployment Solution available at http://www.symantec.com/business/support/index?page=content&id=HOWTO8690

Backup Exec Guide about Agents and Optoins

A nice microsite on BE2010 and his agents and options can be found here

Altiris Agent for Mac 7.1 SP1 HF1 - Adding Support for OS X 10.7 (Lion)

The article can be found here

Activity Center 7.1 SP1 HF2 Rollup

Article URL http://www.symantec.com/docs/HOWTO58413

Symantec Management Platform and Altiris Solutions Support Matrix

• Article URL http://www.symantec.com/docs/HOWTO9965

Enterprise Vault Server Settings Migration wizard

A migration Wizard can be found here

Symantec System Recovery 2011 Service Pack 1 (ex BESR)

I am pleased to announce you that the following eCRT releases have achieved GA milestone on Thursday 8/September/2011.

1) SSR 2011 Service Pack 1 (10.0.1)

Build Number: 10.0.1.41704

WinLogo certification

New Device Support: SATA RDX based drives

Support of Subscription Based license for SSR Server Edition

GEARWorks security fix

2) SSR-MS 2011 Service Pack 1 (10.0.1)

Build Number: 10.0.1.41708

SMP 7.1 SP1 integration

SSRMS scalability fixes - support for 10000 clients

Windows 2008 R2 SP1 & Windows 7 SP1 support

3) SSR-L 2011 Service Pack 1 (2.0.1)

Build Number: 2.0.1.41572

RHEL 5.7, SUSE 10 SP4 platform support

EXT4 File system support

Uploads to FileConnect has been completed. The uploads to LU server is expected to get completed by Friday 9^th September 2011.

SSR-MS 10.0.1 is available on SIM listing.

Backup Exec 2010 R3 - Hot Fixes Released

I am pleased to announce that the following eCRT releases have achieved GA milestone on September 8, 2011:

1) Backup Exec 2010 R3 Hot Fix 159965  (Internal: Nicobar HF12)

Tech Note:  http://www.symantec.com/business/support/index?page=content&id=TECH159965

            Also available via LiveUpdate

2) Backup Exec 2010 R3 Hot Fix 164220 (Internal: Nicobar HF13; “Elephanta”) <= VSphere 5.0 Support!

Tech Note: http://www.symantec.com/business/support/index?page=content&id=TECH164220

            Also available via LiveUpdate

3) Backup Exec Management Plug-In for VMWare (with Virtual Machine Validator)

Tech Note:  http://www.symantec.com/business/support/index?page=content&id=TECH169148

NOT available via LiveUpdate

How does the Altiris Agent know when to delete a package?

The details are captured in the AeXSWDPolicy.xml file located at C:\Program Files\Altiris\Altiris Agent\Software Delivery\.
There’s a section under any given package that has the following values:
cleanupAfter="10080"
postedExpiry="true"
expiredAt="2008-12-19 09:17:51"

Note:  This setting is automatically provided in NS6 and SMP 7.1.  This is not available in SMP 7.0
Expired packages expire the moment a configuration request update provides a config XML that no longer has any task that references the package.  This is starting point for counting down until deletion.  The date is set at that time and then when the cleanupAfter value is reached, the package is deleted.

How to create an Automation Policy to move resources into an Organizational Group

Below is an example of how to set up an automation policy to dynamically add resources to an Organizational Group

1.In the NS7 Console click on Manage and then choose Organizational Views and Groups

2.Right Click on the folder Organizational Views

3.Choose New -> Organizational View

4.In the right hand pane click on New Organizational View and rename the Organizational View to Subnet.

5.Right click on the Subnet Organizational View in the left hand pane

6.Choose New -> Organizational Group

7.In the right hand pane click on New Organizational Group and rename the Organizational Group to 172.xxx.xxx.xxx Group. 

8.At the top of the NS7 Console click on Manage and then choose Automation Policies

9.On the Schedules tab, above the left pane, click on “New policy”.

10. Name the new policy Assign to 172.xxx.xxx.xxx Group and click OK

11. In the right hand pane set the schedule to anything you would like it to be

12. In the details section set the data source to be a Raw SQL query

13. Click on Save changes

14. Click on Edit query

15. Put a query that returns the resources you want to add to the organizational group into the Parameterized Query Pane.

16. Click OK

17. Leave the Evaluation Rule Condition to Run for non-empty data

18. Click on select a job or task

19. Click on the + in front of the folder System Jobs and Tasks

20.  Click on the + in front of the folder Notification Server

21. Click on the + in front of the folder Automation Policy Tasks

22. Choose the Assign to Organizational Group Task

23. Click OK

24. Click on Edit input parameter

25. For Organizational Group select the 172.xxx.xxx.xxx Group in the Custom Value Dropdown

26. For Action click on Must at least contain

27. For Resource choose Results as CSV in the dropdown menu

28. Click OK

29. Click Save Changes button

30. Click Test Automation Policy

31. In the NS7 Console click on Manage and then choose Organizational Views and Groups

32. Click on 172.xxx.xxx group. You will see all of the resources that have been assigned to the group through the automation policy.

EV 10 : Overview of Enterprise Vault licensing

Enterprise Vault uses the Enterprise Licensing System (ELS). To run the associated Enterprise Vault services, you must install a license key file that covers the Enterprise Vault features that you want to implement.

The following types of Enterprise Vault license are available:

• Production license. This license comprises a product base license and any additional feature licenses. When the license file is installed, the functionality of Enterprise Vault depends on the feature licenses that you have purchased.

  Production licenses generally do not have an expiry date.

• Trialware license. With this 30 day license, the full functionality of Enterprise Vault is available, but the functionality is time-limited, as defined by the key.

  When the license expires, the software continues to run in restricted, read-only mode, which allows archived items to be viewed and retrieved, but no items can be archived. Enterprise Vault tasks will not start, and you cannot migrate the contents of personal folder (PST) files to Enterprise Vault.

• Temporary licenses. Temporary licenses are available for 10 day to 90 day duration.

  When the license expires, the software continues to run in restricted, read-only mode, which allows archived items to be viewed and retrieved, but no items can be archived. Enterprise Vault tasks will not start, and you cannot migrate the contents of personal folder (PST) files to Enterprise Vault.

See Obtaining license keys for Enterprise Vault

See Installing Enterprise Vault license key files

See Replacing Enterprise Vault licenses and installing additional licenses

How to obtain the installation download and license keys for Enterprise Vault.

Problem

Symantec Technical Support does not have access to licensing information, Technical Support is not able to provide direct assistance with application licensing.  If assistance is required with licensing, please contact a regional Customer Care representative.  The number for the US and Canada is 1-800-721-3934.
To obtain a Customer Care phone number for other regions around the world, please visit Customer Care Assistance & Information at    http://www.symantec.com/enterprise/support/assistance_care.jsp

Solution

Note: Enterprise Vault license keys and downloads can be obtained by following the steps and/or viewing videos found at the links below.
Licensing:
For new product license keys:
https://licensing.symantec.com/NP-video/New_Purch.html
For product version upgrade license keys:
https://licensing.symantec.com/VU-video/VU_process.html
Frequently asked questions (FAQs) about Software Version Upgrades:      http://www.symantec.com/business/products/licensing/upgrades/faq.jsp
Additional Helpful Links:
Product Activation & Licensing Keys site:
http://www.symantec.com/enterprise/licensing/activation/index.jsp
Licensing Portal User Guide:
http://www.symantec.com/LicensingPortalHelp
Where to find downloads: 

• Symantec FileConnect -  http://fileconnect.symantec.com
• Enterprise Vault 7.5 (2007) and lower "Service Packs": Enterprise Vault Download site

Enterprise Vault Download site:

Enterprise Vault:  http://www.symantec.com/business/support/downloads.jsp?pid=50996

Compliance Accelerator:  http://www.symantec.com/business/support/downloads.jsp?pid=51025

Discovery Accelerator:  http://www.symantec.com/business/support/downloads.jsp?pid=51022

Symantec FileConnect: http://fileconnect.symantec.com
Symantec FileConnect - List of Available Products:    http://www.symantec.com/downloads/fileconnect/index.jsp
     This index is arranged by
                     - Product family
                     - Within each product family, by language.
A serial number is required to initiate the software download through FileConnect.   The serial number will either come with an upgrade or purchase letter.  This serial number is specific to the FileConnect site and is not the Enterprise Vault license key.  The serial number can be found in the license file (.slf) located on the EV server in \Enterprise Vault\Installed Licenses.  Open the .slf file in Notepad. The following line will show near the top of the file, and the serial number is the letter followed by 10 digits.
<serial_number>M0123456789</serial_number>
If this information is not available, a serial number can be procured from:
           Symantec Licensing Portal:
https://licensing.symantec.com/acctmgmt/index.jsp
           or request a FileConnect serial number through Symantec Customer Care:
http://www.symantec.com/enterprise/support/assistance_care.jsp
Because application downloads require access to licensing information to which Technical Support does not have, Technical Support is not able to provide assistance with application downloads.   If assistance is required with either of the two download locations, please review the licensing PDF documents as referenced in the Licensing section above. 
If further assistance is required, please contact a regional Customer Care representative.  The number for the US and Canada is 1-800-721-3934. To obtain a Customer Care phone number for other regions around the world please visit Customer Care Assistance & Information at      http://www.symantec.com/enterprise/support/assistance_care.jsp

EV10 Landing Page

http://www.symantec.com/business/support/index?page=landing&key=50990

EV10 Tech Center

http://techcenter.symantec.com/ecampus/enterprise?siteName=sena&courseNo=DP6002

Commonly Used Articles for Deployment Solution 7.0, 7.1, 7.1 SP1. (Work in progress)

A very nice landing page for DS7.X can be found here

DS7.x How to add NIC and Mass Storage drivers to Preboot Configurations and/or DeployAnywhere.

Why it may be Needed

This is required when drivers are needed that are not already bundled into the WinPE build.
Common Symptom:

The most common manifestation of a missing driver is the inability to boot to WinPE with the error: "Restarting DHCP client service retry 1..." which will repeat 19 times before giving up and booting without network support. This generally indicates that a driver required for the NIC in the system booting to WinPE is missing, and can't bind correctly to the card, thus can't send a valid DHCP request.

Procedure can be found here

DS 7.1 SP1 Technical Document: Architecture & Dataflow

Nice article can be found here

Bandwidth throttling and speed tests, how does it work?

Ever wondered how the bandwidth throttling is working?

Click here to find out more

Symantec Management Platform and Altiris Solutions Support Matrix

The Support Matrix got updated a bit and can be found Here

Patch Management 7.1 SP1

Client Management Suite Now Includes Broader Patch Coverage

Altiris Client Management Suite 7.1 extended its patch management coverage by adding support for 24 commonly used third-party Windows applications with the recent release of Patch Management Solution 7.1 SP1. This release helps customers address a top priority risk according to SANS -- unpatched client-side software. The release also includes:

Updates to Microsoft applications and operating systems
Support for security and non-security related updates (including service packs)
Improved IT Analytics with trend reporting capability that lets administrators track key performance indicators with respect to updates from both Microsoft and supported third-party vendors
Simplified configuration with a First Time Setup Wizard