using Group Policy to assign an installation

Discussion in 'AutoCAD' started by bstaples, Oct 28, 2004.

  1. bstaples

    bstaples Guest

    Has anyone had any luck with using AD and group policy to assign an installation and been successful? I have read through the networking admin guide, section C pages 69-74. I have done the exact steps but when I reboot a target station, I see quickly a message about ADT2005 beginning to setup but then it's finished after a few seconds and the logon screen appears. I log in but there is no icon to click on as specified on page 74.

    In the event viewer application management errors are recorded. One will say "failed to apply changes to software installation settings, software changes could not be applied" The other says "The install of application ADT2005 from policy failed. The error was: The install source is not available, check the source exists and you can access it"

    I can then connect to the server where the deployment resides and I can see get into the folders fine. The only thing preventing me from going further is when I try to run the deployment it tells me I need admin rights.

    I would appreciate any insight to this as I would love to be able to assign the installs to new workstations without having to give users any extra rights to run installs.

    Brian
     
    bstaples, Oct 28, 2004
    #1
  2. Your users should not need administrative rights to their workstations. I
    suspect an access problem. I would start by allowing full control of the
    location where the deployment resides and its subfolders to everyone. If
    that helps then you can experiment on locking the folder down a bit.


    --
    Jerry Milana,
    Autodesk Consulting

    installation and been successful? I have read through the networking admin
    guide, section C pages 69-74. I have done the exact steps but when I reboot
    a target station, I see quickly a message about ADT2005 beginning to setup
    but then it's finished after a few seconds and the logon screen appears. I
    log in but there is no icon to click on as specified on page 74.
    say "failed to apply changes to software installation settings, software
    changes could not be applied" The other says "The install of application
    ADT2005 from policy failed. The error was: The install source is not
    available, check the source exists and you can access it"
    see get into the folders fine. The only thing preventing me from going
    further is when I try to run the deployment it tells me I need admin rights.
    assign the installs to new workstations without having to give users any
    extra rights to run installs.
     
    jerry milana \(Autodesk Consulting\), Oct 28, 2004
    #2
  3. Yes,

    the GPO installs the .msi packages with system rights.

    I'm not sure about ADT2005, I only have installed AutoCAD2005 with GPO.
    There the problem was at first that 2005 need .NET Framework installed
    before it will install. Dotnet.exe can be downloaded from Microsoft and
    extracted, inside is netfx.msi and netfx1.cab. We installed them with GPO
    and after that the 2005 installation also succeeded.

    For our own modifications we made a .msi. We also made a .msi of the AutoCAD
    files in user cache that are normally copied under each profile and
    installed them under AutoCAD so that they are always in standard locations.

    Juha

    installation and been successful? I have read through the networking admin
    guide, section C pages 69-74. I have done the exact steps but when I reboot
    a target station, I see quickly a message about ADT2005 beginning to setup
    but then it's finished after a few seconds and the logon screen appears. I
    log in but there is no icon to click on as specified on page 74.
    say "failed to apply changes to software installation settings, software
    changes could not be applied" The other says "The install of application
    ADT2005 from policy failed. The error was: The install source is not
    available, check the source exists and you can access it"
    see get into the folders fine. The only thing preventing me from going
    further is when I try to run the deployment it tells me I need admin rights.
    assign the installs to new workstations without having to give users any
    extra rights to run installs.
     
    Juha Hänninen, Oct 29, 2004
    #3
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.