IT Quality Assurance specialists are tasked with making sure a product hits the theoretical mark, but high quality testing takes a lot of time. One thing that has boggled my mind working with enterprise software vendors is their insistence on creating users manually in a software testing environment.
There are valid preferences for a manual setup of new user accounts including training, but adding 1,000 users with this process can require many hours work for up to 3 or more staff in a complex corporate environment due to legal separation of duties and multi-platform security hierarchies. Considering enterprise software normally costs millions in implementation and licensing, manual setup processes for user accounts is a complete waste of time, in turn, money.
Why not automate this process by creating 1,000 users from 1 in SQL Server and Active Directory (AD). There are a few applications available for purchase which accomplish similar results, but many experienced systems integrators will prefer on-the-fly creation since troubleshooting is usually required either way. I’m linking out to a couple of posts I found on AD creation at this link and SQL user creation at this link. It will be up to you if you want 1 permission set for all accounts or a few different account types making security more realistic. Multiple security roles will require multiple runs of this process.
AD and sAM permissions get hairy enough on their own so I suggest starting with AD:
- Run AD creation giving it time to replicate through the network to multiple domain controllers (sync time is set by administrator)
- Export users names to an Excel file using AD tools (your administrator may have to give you this info)
- Create a temp table in your database on the same AD domain
- Import user names to the temp table through SQL Enterprise Management Import GUI
- Now begin the SQL user creation process (use a left-join SQL select within your SQL to join the user name in your temp table to the user creation script)
This won’t help if your vendor is “closed” meaning they require a proprietary encryption key or sequencing when user accounts are created in SQL. I have seen this problem since many hospitals are all about auditing user accounts. Audit trails are dynamically tied together in a database. Any change to audit trails purposely locks the user record or requires an encryption key prior to access. Short answer – you can’t change this.
Wireless is just another medium for data, but some wireless routers are completely locked down for security reasons such as malware and DoS attacks. Your network administrator may need to allow certain ports in and outbound traffic for all Windows permissions to propogate properly.