8/17/2012 10:28:17 AM
 Nick S Posts: 25
|
Anyone have good deployment practices they'd like to share?
Alternatively, anyone have horror stories of bad deployment ideas that burned them that I should avoid?
One concept I'd like to bat around is deploying SS initially with limited functionality (no auto-password changing, discovery, expiry, etc.).
I'd like it initially to be basically a password wallet.
I'd like to then, at a later date, slowly unroll features to my users such as discovering dependencies and doing auto password management.
Will I be painting myself into a corner or wishing I would've done things differently once I get to the point of rolling out these features?
I just don't want to start down one road, have a ton of secrets put into the server and then go to enable some functionality only to find I have to "touch" each previously stored secret to enable something or other, etc.
Does that make sense?
Feel free to share any deployment plans that you might have!
Much appreciated!
|
|
|
0
• link
|
8/17/2012 10:58:39 AM
 Jonathan Administrator Posts: 591
|
Nick,
Here is an implementation plan that we put together based on seeing customer adoption experiences over the years... <a href="http://www.thycotic.com/articles/ImplementationPlan.pdf">http://www.thycotic.com/articles/ImplementationPlan.pdf</a>
It is pretty high level but may help thinking it through.
Typical timeline for an enterprise customer to fully implement the plan could be from 1 month to 6 months (the tech is usually the easy part - the hard part is dealing with all the politics and internal controls! :-D).
Best.
-- Secret Server 8.1 - Web Password Filler, SAP support, advanced discovery capabilities with rules. Need a free trial license? Send an email to sales@thycotic.com
|
|
|
0
• link
|
8/17/2012 11:28:37 AM
 Nick S Posts: 25
|
Definitely high level but appreciated Jonathan, thank you!
If anyone else has random tips I'd love to hear them!
|
|
|
0
• link
|