Some feature requests

[Anton Chernomazov]

Server:
* Active Directory authentication (yes, i'm tooo lazy to remember and to change two more passwords )
Console Interface:
* Double-click on anything editable item should call editing dialog for this item. Don't Enter pressing only. It's so simple to implement, and it's so pleasantly to use.
* Why do i have to set partner's authentication parameters after HA target creating? What about Target creation wizard?

[anton (staff)]

1) There's no connection between AD and StarWind so I personally have no clue where to start from. Could you please clarify?

2) Well... OK!

3) How do you see it? Step-by-step please.

Thank you!

Server:
* Active Directory authentication (yes, i'm tooo lazy to remember and to change two more passwords )
Console Interface:
* Double-click on anything editable item should call editing dialog for this item. Don't Enter pressing only. It's so simple to implement, and it's so pleasantly to use.
* Why do i have to set partner's authentication parameters after HA target creating? What about Target creation wizard?

[Anton Chernomazov]

1. I mean using AD to authenticate Starwind server administrator (administrators) when connecting to management console.
3. Now (am I wrong?):

• Giving target alias
• Choose HA target type
• Specify partner server parameters (I use Basic authentication)
• Specify partner target
• Specify disks' parameters
• Specify network parameters

Request:

• Giving target alias
• Choose HA target type
• Specify partner parameters (I use Basic authentication)
• Specify partner target
• Specify partners' authentication parameters
• Specify disks' parameters
• Specify network parameters

Is this request stupid or wrong?

[anton (staff)]

1) I'm not sure it's a very good idea but I'll talk to our GUI guys in any case.

3) I don't think it's stupid so again I'll talk to GUI guys

1. I mean using AD to authenticate Starwind server administrator (administrators) when connecting to management console.
3. Now (am I wrong?):

• Giving target alias
• Choose HA target type
• Specify partner server parameters (I use Basic authentication)
• Specify partner target
• Specify disks' parameters
• Specify network parameters

Request:

• Giving target alias
• Choose HA target type
• Specify partner parameters (I use Basic authentication)
• Specify partner target
• Specify partners' authentication parameters
• Specify disks' parameters
• Specify network parameters

Is this request stupid or wrong?

[anton (staff)]

OK, discussed listed features with head of R&D and updated our schedule just a bit.

1) Active Directory authentication. ~V6.0 (Fall 2011).

2) Wizards re-work (and partially in the way you've listed). ~V5.8 (Summer 2011).

3) Click-Edit stuff. We're adding / fixing controls one-by-one. So ETA is now

Anything else you'd like to see implemented / altered?

Thank you for your feedback!

Anton

[clayton@mcc911.org]

As for the AD idea

have you ever use the MegaRAID Storage Manager (MSM) LSI utilty? the adaptec raid manager is the same way.
after you install the program , when you log in you just use an admin accout on the local machen or a AD admin account if it part of a domain.

its really nice to just beable to use the admin accout you have and not set up a new one.
i remember the first time i loaded it, and the login box comes up and i tryed the fast four, root-root admin-root root-admin & admin-password
then googled the MSM default password and was so pleased when it said it uses existing local and domain admin accounts.

just my 2cents.

[Anton Chernomazov]

anton (staff)
Thank you for rapid decisions.

I'll let you know about any feature requests as soon as they will appear.

clayton@mcc911.org
You're right! It seems excessively to set up Starwind server's connection with AD when OS is in AD already.

[Anatoly (staff)]

Great!

We`ll wait for your update.

[anton (staff)]

Very nice consideration. We'll definitely have this one implemented. Thank you for confirming

As for the AD idea

have you ever use the MegaRAID Storage Manager (MSM) LSI utilty? the adaptec raid manager is the same way.
after you install the program , when you log in you just use an admin accout on the local machen or a AD admin account if it part of a domain.

its really nice to just beable to use the admin accout you have and not set up a new one.
i remember the first time i loaded it, and the login box comes up and i tryed the fast four, root-root admin-root root-admin & admin-password
then googled the MSM default password and was so pleased when it said it uses existing local and domain admin accounts.

just my 2cents.

[Anton Chernomazov]

I don't see anything similar in v5.6.1667.

[anton (staff)]

You should not. We did not implement one yet.

I don't see anything similar in v5.6.1667.

[hixont]

Personally I like the ability to limit administrative access to the Starwind server. I don't currently trust my fellow domain admins to administer the SAN and I certainly don't trust my AD forest admins with this ability.

[Aitor_Ibarra]

Hixont: I hope your domain admins don't read this forum!

The big question is: do you trust them with your entire network infrastructure? So many things depend on Active Directory that really you shouldn't have incompetent or malicious people in charge of it...

Anyway, your problem could be solved if Starwind retains existing security and adds Windows/AD as an option. You could then decide which Windows/AD account to delegate admin priveledges to - e.g. you could create an AD group called Starwind Admins... and not make your Domain Admins members. Of course, as Domain Admins, they have the power to make themselves members...

[Anton Chernomazov]

Personally I like the ability to limit administrative access to the Starwind server. I don't currently trust my fellow domain admins to administer the SAN and I certainly don't trust my AD forest admins with this ability.

If StarWind Server is domain member, domain admins and forest admins have too more power already (to shutdown/reboot server, to stop/restart service, to edit config files/registry, etc.).
It's simpler don't make StarWind Server domain member.

[Anatoly (staff)]

Agree to Anton.

But if StarWind machine is already in domain you can use CHAP and/or ACL