{"id":1359,"date":"2012-07-31T04:00:39","date_gmt":"2012-07-31T11:00:39","guid":{"rendered":"http:\/\/blog.brainlitter.com\/?p=1359"},"modified":"2012-07-31T04:00:39","modified_gmt":"2012-07-31T11:00:39","slug":"sharepoint-service-account-creation-worksheet","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2012\/07\/31\/sharepoint-service-account-creation-worksheet\/","title":{"rendered":"SharePoint Service Account creation worksheet"},"content":{"rendered":"

\"image\"<\/a>When providing guidance to customers about SharePoint Service accounts (lots of posts out there already, so I\u2019m keeping this short), we end up submitting a recommend service account list (they don\u2019t always go for them, but we do our best at trying to do the right thing).<\/p>\n

Anyways, SharePoint Service accounts ideally will have several characteristics (beyond strong passwords, changing them regularly, etc. which are good policies) including:<\/p>\n

 <\/p>\n

    \n
  1. Passwords greater than 14 characters \u2013 yep, I\u2019m a meanie \"Winking<\/li>\n
  2. Username length (not the UPN but the NTPre-Windows 2000 username) should be readable under 20 characters. In other words, if you submit a long username to your IT Department and they paste it in the field, a shorter username is going to get created (and often we find, it isn\u2019t effectively communicated to us)<\/li>\n<\/ol>\n

    The following worksheet was created to help manage this.\u00a0 And you are welcome to it (get it here<\/a>).<\/p>\n

    \"image\"<\/a><\/p>\n

     <\/p>\n

    Enhancements you might want to make:<\/h4>\n