|
| | | Junior Member
 
Group: Forum Members
Last Login: 10/25/2006 3:31:08 AM
Posts: 12, Visits: 37 |
| (1.) At this point we create a lot of configuration groups based on edited "predefined" groups. Especially file versions (which we use to deploy patches to). Al these are located in root. Custom groups are created in a subfolder. The screen gets cluttered with different kind of groups and gets somewhat incomprehencible (I try to use some prefixes like zzz_Office_2000_ update_Powerpoint).I would like to build a hierarchical layout with multiple levels. Something like this:
+ Standard software (manual)
+ Office 2000 (manual)
- Standard implementation (manual)
+ Updates 2006-6 (manual)
+ "C:\Program Files\...\powerpnt.exe" (predefined)
- ""
- "C:\Program Files\...\powerpnt.exe" = "9.0.0.6620"
- "C:\Program Files\...\powerpnt.exe" = "9.0.0.8942"
- Updates 2006-7 (manual)
+ Adobe reader (manual)
- Version of acrord32 (predefined)
- ""
- 7.0.0
+ 7.0.8
- machine1
- machine2
+ Special Software (manual)
+ Version of Package XYZ (predefined)
- Version 1.1
- Version 1.2
(2.) I would like a differerent Icon for config groups WITH a task assigned and config groups WITHOUT a task assigned. Suggestion: something like an arrow
(3.) Active Directory. When a workstation is moved within AD, we have to delete Workstation and reinstall from network window. I would like to have client report or move itself accordingly
That that doesn't kill me, only makes me stronger! |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810 |
| | Thank you for feature requests #1 and #2. I've circulated these to our product planning group and entered them into our feature tracking database. Regarding #3, a computer that is polling the Channel using its Active Directory name (and thus is a member of an organizational group in the Console) should create and move to a new organizational group when it is moved within Active Directory. Note: When you move a computer to a new OU, you must reboot the computer to make the change visible in the Prism Console. What version of Prism are you using? Is there anything unusual about your process of moving a computer to a new OU?
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Junior Member
Group: Forum Members
Last Login: 10/25/2006 3:31:08 AM
Posts: 12, Visits: 37 |
| #3. We move a workstation with ADUC (AD is w2k). I suppose the normal way is Right mouse click, select move and then a new location. Clients use version 7.1.3.23. I confirmed workstations ARE using "Use Active Directory" = 1 Reg-key. Prism version is 7.0.4.23. I have no idea why it doesn't work.
I tried rebooting workstation several times, refreshing console, restarting console.
The console keeps showing workstation in old OU (the registry of this workstation also shows the old full computername in .... \prism...\channelGUID\.. etc.)
Mario
That that doesn't kill me, only makes me stronger! |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 10/8/2008 1:15:23 PM
Posts: 655, Visits: 810 |
| We recommend you investigate issues with the computer's DNS settings. If the computer can't report its new AD name in Prism, perhaps it is pointing to the wrong DNS server(s). I've confirmed in our lab that this would cause the problem you're seeing.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|