(/resources/ce_4.1/html/ALIAS/DirectConnect_2011/Readme/DirectConnect_2011_Readme.html) Product Name Readme
Notice to Autodesk DirectConnect Customers: DL15200805 Release

In our continuing efforts to provide high quality products, Autodesk has released hotfix DL15200805 which addresses issues with JTfiles.

This readme contains the latest information regarding the installation and use of this update. It is strongly recommended that you read this entire document before you apply the update to your product. For reference, you should save this readme to your hard drive or print a copy.

Contents

Return to Top

Supported Operating Systems

For application of this hotfix, your system must have one of the following products installed:

Return to Top

Description of Resolved Issues

This section provides a description of the issues that have been resolved with this release.

This hotfix should only be applied to systems directly affected by the issue described above, as this was the only issue this hotfix was created to address.

Return to Top

Installation Instructions

Individual machine installation for 32bit users

Follow these instructions to install hotfix version 5.0.598.0 (336445) with the build date of Tue May 11 03:15:38 2010 over the DC2011 release version that was installed with AliasStudio 2011.

  1. Click setup.exe.

    Note You should not need to uninstall DC2011.

  2. Click Finish.

Individual machine installation for 64bit users

Follow these instructions to install hotfix version 5.0.599.0 (336445) with the build date of Tue May 11 03:15:20 2010 over the DC2011 release version that was installed with AliasStudio 2011.

  1. Click setup.exe.

    Note You should not need to uninstall DC2011.

  2. Click Finish.

Group installation

Follow these instructions to deploy the software using group policies for Windows.

Disclaimer

The description of methods presented here is provided to aid those looking for a straight forward, Microsoft supported means for deployment of software over a Local Area Network. If the Microsoft Group Policy based mechanism does not provide sufficient control or features for the size or complexity of your network environment, we recommend that you consider more advanced Microsoft solutions, or other third party solutions.

Introduction

Microsoft’s Active Directory technology provides the capability for software to be remotely installed from a server distribution point to client computers. The client computers must be members of an Organizational Unit (OU) in the Active Directory. Software deployment is controlled by configuring the Software Installation policy of the Group Policy Object (GPO) associated with that OU. The software installation occurs automatically at boot time; no user intervention is required.

Prerequisites

Configuration process

There are three main steps to deploying software using group policies:

  1. Create a Distribution Point.
  2. Assign the application to client computers.
  3. Verify the installation.

    NOTE: Consult Microsoft Knowledge Base Article #816102 for more details, including information on how to redeploy or remove a package.


Create a distribution point

A distribution point is a shared network location containing the package(s) to install.

To create a distribution list

  1. Log on to the appointed server as Administrator.
  2. Create a shared network folder.
  3. Grant permissions as appropriate. Permission to modify the contents of this folder should typically be granted to an administrator or select group of users; all other users should be restricted to read access.
  4. Copy the .msi files for the package(s) to be deployed into this folder.


Assign a package to client computers

The Software Installation section of the Group Policy Object specifies the software packages to be deployed.

To assign a package for deployment

  1. From the Windows Start menu on the server, click All Programs (or Programs) > Administrative Tools > Active Directory Users and Computers.
  2. Browse to the desired Organizational Unit (OU) in the Active Directory tree, right-click, and click Properties. The Properties dialog box for the OU selected displays.

    NOTE: For the Group Policy Object to take effect, the desired client computer objects must be members of the OU selected.

  3. Select the Group Policy tab and click New. Enter a name for the GPO. For example, “Alias Computer Assigned Installation”. The GPO is created and added to the Group Policy Object Links list.
  4. In the Group Policy Object Links list, click the GPO you just created, then Edit.
  5. In the left pane of the Group Policy Object Editor, under computer Configuration, click the plus sign (+) next to the Software Settings folder to expand it.
  6. Under Software Settings, right-click Software Installation, then click New > Package.
  7. Enter the UNC path to the desired package located in the distribution point created in the previous section, then click Open. For example, \\server\share\Alias.msi

    NOTE: Do not browse to the network location. You must type the UNC path into the “File name” text box.

  8. Select Assigned and click OK. Wait until an entry for the package is displayed in the right pane of the Group Policy window.
  9. Repeat steps 7 and 8 for all packages to be deployed.
  10. Close the Group Policy window and any other open Active Directory windows.

    The package is now assigned to all computers that are members of the OU for which the GPO has been created. The next time a computer in the OU is restarted, the program will be installed and available for all users of the computer.

    NOTE: Windows XP is shipped with Fast Logon Optimization enabled. Due to this feature, two reboots are required before the software will be installed. Microsoft Knowledge Base Article #305293 describes the Fast Logon Optimization feature, along with instructions on how to disable it.

Test and verify the deployment

When a computer is restarted, the operating system displays messages about group policy, generally just before or after the Windows Login dialog box is displayed. These messages include the following:

To verify that the package has been correctly assigned to a computer, restart a computer that is in the OU for which the GPO was created. The program is installed during the boot sequence, before the login prompt is displayed. After logging in, the user should find the application under the Programs menu in the same location as if it had been locally installed.

NOTE: If problems arise, an entry is logged in the system’s Event Viewer under Applications.

References

Return to Top

Copyright © 2010 Autodesk, Inc.