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

SMP 7.1 Platform Database Schema

The Database Schema can be found here

ITMS 7.1 SP1 is out

The release notes can be found here

A nice landing page can be found here

Map Values to Altiris Asset Management and Helpdesk Solutions

Introduction

This white paper will outline the technical aspects of leveraging an organizations investment in Microsoft Active Directory and Altiris solutions such as the Active Directory Connector, Inventory Solution, Asset Management and Helpdesk solutions. It will focus on how to create new resource types within Active Directory and the Altiris CMDB and export the information from Active Directory to be imported and mapped to Altiris Resources to be made available for use with other Altiris Solutions. This ability improves the integration of Altiris and Microsoft while reducing time of manually entering data into Altiris, reducing human typographic errors and reduces likely errors from incorrect or missing updates.

http://www.symantec.com/connect/articles/map-values-altiris-asset-management-and-helpdesk-solutions

KNOWN ISSUE: Many files, registy keys and values, and directories are not removed when Symantec Management Platform is uninstalled

A file to solve this issues is available to download here

ITMS 7.1 SP1 documentation Landing Page

Most release notes on Platform, CMS, SMS and ITMS can be found here

http://www.symantec.com/business/support/index?page=content&key=55274&channel=DOCUMENTATION

Microsoft SCEP Implementation Whitepaper (for MMS).

This paper can be found Here.

Workflow Solution 7.1 Known Issues and Associated KB Articles for All Builds

A nice article on the known issues and Release Notes can be found here

BE2010R3 Releases on 2de of may

We are excited to announce that Backup Exec 2010 R3 is now GOLD!

New features include:

· Virtual Vault support for the Archive Option

· Support for protection of Enterprise Vault v10 when released

· Improved DeDuplication rates for VMware images

Supportability and customer satisfaction improvements include:

· Install enhancements based on telemetry data

· Install-integrated NPS survey

· Virtual agent updates

· DeDuplication updates, including the PDDE team’s Rock Solid efforts

Backup Exec 2010 R3 (build 5204.4) will be released into First Availability within the week.  RTM is April 25, with GA following on May 2. 

How to create a Pre-defined Computer using only a MAC address in DS 7.1

Please read the attached document, "How to create a Pre-defined Computer using only a MAC address in DS 7.1" for details.

Attachments

this is the actual article that describes how the process is done

How to create a Predefined Computer using MAC address only in DS 7.1.docx (111 kBytes)

This is the Pectagent for DS 7.1 up to and including MR4 (32bit version of NS/DS)

PECTAgent.exe (610 kBytes)

This is the X86 Pectagent for DS 7.1 sp1 build 1374 (64bit version of NS/DS) • C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\bootwiz\oem\DS\winpe2\x86\Base\Program Files\Altiris\Altiris Agent

PECTAgent.exe (610 kBytes)

/apps/media/inquira/resources /resources

This is the x64 Pectagent for DS 7.1 sp1 build 1374 (64bit version of NS/DS) • C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\bootwiz\oem\DS\winpe2\x64\Base\Program Files\Altiris\Altiris Agent

PECTAgent.exe (610 kBytes)

Related Articles

• DS 7.1 Predefined Computers boot to production ("Next Device") or initial deployment instead of the correct PXE menu option.

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

SEP 11.0, RU6 MP3 is Released

 

This build's version is: 11.0.6300.803.

This build's information is located here.

This build's zipped DVD files can be downloaded from here.

This build's Release Notes: Release_Notes_SEP_11_RU6_MP3.pdf.

This build's Fix Notes: Fix_Notes_for_SEP_11_RU6_MP3.docx.

ITMS 7.1 SP1

The intention is there to support WIN2008r2SP1 in ITMS7.1SP1 at the end of may, but if any issue is found it will not be in this release.

Mobile Management is NOT yet available for ITMS7.1

Mobile Management is only available for ITMS7.0 and a SP4 is scheduled for Q3 2011.

When there will be a version for 7.1 is not clear yet

WIN2008r2 SP1 is NOT supported for ITMS7.1 till further notice

WIN2008r2 SP1 is not yet supported for ITMS7.1.

As soon as it changes I will make a note in the blog.

Getting the hang of IOPS

Very very good article that everyone should read…

http://www.symantec.com/connect/articles/getting-hang-iops

Facts About Combine License Workshop

http://www.symantec.com/connect/articles/facts-about-combine-license-workshop

 

The License Workshop can be used to download the licenses for all Altiris products registered to your company (or group of companies), or to combine and download licenses for a particular Altiris product.

Combining Licenses

When two or more license certificates for the same product are combines into a single certificate, the new maintenance date that is embedded in the certificate is the lesser of all the dates.

For example, if you combine 100 nodes of a product with a maintenance date ending 01-01-2007 with 100 nodes with a maintenance date ending 06-01-2007, the new certificate will be created for 200 nodes with a maintenance expiration date of 01-01-2007.

When the maintenance expires on the combined license you can use the License Management Portal to received your licenses in a new configuration, or you may contact your Sales Representative to have your maintenance dates co termed to a single date.

During the co terming process, the maintenance expiration dates on combines licenses will also be combined. All combined licenses will assume the shorted maintenance duration available from the individual licenses.

Example, if you combine two license files, one having 6 months remaining and the other having 8 months remaining, the maintenance window of the combined license files will have a maintenance duration of 6 months) At the end of the combined licenses term, you will have the opportunity to use the remaining two months of support in the example by installing the individual license key containing the remaining maintenance.

The Maintenance assigned to the license is the lesser of the Maintenance dates assigned of the licenses being combines or 7 months from the day the license is being created. When licenses are, the .txt files must have at least 7 months of Maintenance assigned or the license will timed out.

Using the License Workshop

* Option 1
Allow you to download the licenses for all your Altiris products at once. When choosing this option, the system will automatically combine licenses for products you own into as few license files as possible, placing the licenses into a single ZIP file that is downloaded to your computer.

The licenses downloaded will be for all Altiris companies associated with your Symantec account, and is not affected by the check boxes show in the Option 2 area of the page.

* Option 2 Download Selected Licenses (Combined)

When more than one Altiris company is associated with your account, a list of those companies will be displayed on the page. New license purchase with your Symantec account will be listed under the name ' New Licenses'. (There may be multiple companies listed due to grouping that was done in Altiris, and also grouping that was done when Altiris information was moved to Symantec)

Using the check boxes nest to the company names, choose the companies associated with the products to be combined (to keep things simple, you may wish to leave all companies selected) . As you change the selected companies, the list of products will change to show all combinable products for the selected companies. If there is only one company associated with your account, you will not be able to deselect it.)

Next select a product to combine from the list of products- only combinable products with active support will be listed. Please not that only individual products are combinable- suites of products are not.

Finally, combine the desired licenses using the arrows, and click on the download button to obtain a single combined license file for the selected product (the maintenance co termination rules noted above will apply.)

Remote Altiris Agent Diagnostics 2.0 (RAADv2)

How do I remotely troubleshoot an agent without logging into the machine?

"Remote Altiris Agent Diagnostics" (RAAD) version 2 expands on the diagnostic checks and remediation actions performed by RAAD version 1 (KB 45023) to allow those checks and actions against a list of machines and not just the one machine. The Health Checks in RAAD version 2 are designed to take a look at the state of the Altiris solution plug-ins such as Patch, Task, SWD and Recovery to determine if they are working properly. Version 2 also allows the ability to run a Custom Inventory XML against the set of machines and return the results immediately so you can customize your own health check. You can examine more in-depth details of the Agents using the Diagnostics tab which is essentially RAAD version 1. The biggest advantage with version 2 is that you can run remediation actions such as Configuration Request and Start Patching Cycle against as many machines as you'd like and all at once.

The process is to get a list of machines, run a health check against them, then by evaluating the results or drilling down into the diagnostics choose a remediation action to run against the machines you choose.

Features:

• Diagnostics and Health Checks
• x86 and x64 compatible for remote clients
• Ability to pass credentials used to connect to remote clients
• Multi-Threaded
• Agent, sub-agent, and customizable Health Checks
• Ability to run an action against multiple remote clients at once
• Customizable User Interface and captured

* Please see KB 45023 for application functionality

Download:

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

Requirements:

• Run the executable locally, not from a share
• Host and remote machine must be Windows OS
• Do not use 'Run As' - you can pass credentials in this version
• .NET 1.1 framework installed on host and remote machine
• Altiris Agent must be installed on host
• Firewall on the remote machine will also prevent Altiris actions.

  You will need to add AeXNSAgent.exe to the Firewall exclusion by running the following command on the remote machine:

  netsh firewall add allowedprogram "%programfiles%\Altiris\Altiris Agent\AeXNSAgent.exe" ENABLE

  
  
  

  Or you can simply run this command from the 'Remote Execute Option' button from the application

  
  

Usage:

To distribute desired application settings such as Remote Execute options edit the RAAD.exe.config and place it in the same folder as RAAD.exe. If user has altered application settings have them go to Settings - Change Application Settings and choose Restore All Setting to Default which will import your altered RAAD.exe.config.

pcAnywhere Diagnostic and Connect Tool v1.0013

pcAnywhere Diag Features

• Encrypts and stores connection and diagnostic credentials
• Remembers the last PC connected to
• Ability to store a favorites list
• Single click to modify, double click to set as connection PC
• Checks the client status and repairs any issues
• Eliminates the “Raising Encryption” message upon connect
• Works even if the Altiris console is unavailable

Link to the article can be found here

Deployment Solution Samples for v7.1 SP1 (on SMP/CMS 7.1) x64

Well, it was a long time coming, and it's not 100% perfect.  Call this a public BETA of sorts.  Support was given permission to release a set of Deployment Samples for the current shipping code.  This set is an x64 installation and thus will not run on previous versions of the product.  The XML files that it extracts MIGHT work on previous versions, but of course it will be use-at-your-own-risk.  (Truthfully, MOST of it should work fine, but we don't have time to test it).

A link to this article can be found here

Web Page for Enabling Support to Deploy Tasks or Packages to Specific Machines in NS7

Do you ever need to push a package out to a single computer but the hassle of creating a job in the console takes too long? Wouldn't you like to give desktop support or the helpdesk this ability and still control what packages they can deploy? Then this is the answer to all you have hoped for! We've been using this page for months now on NS7 and it rocks!

Link to tis nice article can be found here

DS 69SP5 is available here

You can find the download for DS69SP5 here

The Release Notes can be found here