1 Reply Latest reply on Aug 16, 2004 8:05 AM by GUGU

    Deploy Plan Suggestion

    Joe1 Apprentice
      Provide a menu item for a project that would show on one page (if not a single screen) all the various elements of a project's deployment.  This would include project execution properties, all permissions at any level they are set, all schedules for various levels, and where a project is replicated to.

      Example 1:
      Project A Deployment Information
          Installation: TUS

      Permissions:
      Org:
      Interactive: *
      Auto: Group="Project A"
      Schedules:
          AutoInstall: None
          Interactive: Beginning at 7:00 a.m. on 12/1/2003
      Replication: N/A

      OU-PROD-A:
      Interactive: *
      Auto: Group="Project A" + RAM =>512 MB
      Schedules:
          AutoInstall: Beginning at 7:00 a.m. on 1/1/2004
          Interactive: Beginning at 7:00 a.m. on 12/1/2003
      Replication: Yes

      OU-PROD-B:
      Interactive: *
      Auto: Group="Project A" + RAM =>512 MB
      Schedules:
          AutoInstall: Beginning at 7:00 a.m. on 2/1/2004
          Interactive: Beginning at 7:00 a.m. on 12/1/2003
      Replication: NONE


      Example 2:
      Project B Deployment Information
          Installation: TUS

      Permissions:
      Org:
      Interactive=*
      Auto="Project B"
      Schedules:
          AutoInstall: None
          Interactive: Beginning at 7:00 a.m. on 12/1/2003
      Replication: Site Groups: Group X, Group Y

      OU-PROD-A:
      Interactive: *
      Auto: Group="Project B" + RAM =>512 MB
      Schedules:
          AutoInstall: Beginning at 7:00 a.m. on 1/1/2004 (weekly)
          Interactive: Beginning at 7:00 a.m. on 12/1/2003
      Replication: Yes

      OU-PROD-B:
      Interactive: *
      Auto: Group="Project B" + IsUser("TestID")
      Schedules:
          AutoInstall: NONE
          Interactive: Beginning at 7:00 a.m. on 12/1/2003
      Replication: NONE


      Example 1 shows how, without drilling to OU-PROD-A one would not know that an additional criterion had been set for AutoInstall permissions on Project A.  It would also show the different AutoInstall schedules that had been applied, even though none are displayed at the ORG level when you check the schedules.

      Example 2 shows how a permission, i.e. IsUser('TestID') set at an OU during testing can readily be overlooked once a project is set for production. 

      In both examples, if replication is not set for OU-PROD-B, this is reported.

      In an Enterprise, where more than one Administrator is likely to be working on or attempting to resolve deployment issues, one or another admin may not be aware of the permissions and schedules set below the Org level, the only location where they are immediately apparent.

      This would tremendously enhance diagnostics when determining why a project did not install as expected.  Otherwise, the administrator must obtain a log file from a client at a location and, if logging is in debug mode, determine from that why the project does not install. 

      The permissions and schedules interfaces are very handy when setting a project up, but it is difficult to review afterward to see where these are set.
        • 1. Re: Deploy Plan Suggestion
          GUGU Apprentice
          nearly the same question we have posted in the german newsgroup. we have 5 admins working with netinstall to support 150 terminal servers. sometimes with software releases we want to know what projects are released for the next 10 days. So all the informations Joe posted are relevant.