- Pre-install Setup Guide – Windows 7
- Pre-Install Setup Guide
- Permissions To be SET prior to SQL Server Installations
- Elevate Current User to SQL Server Admin
- Adding Debug Permissions To User
- Disable DEP and Enable PAE
- Windows Defender Removal in XP and Vista
- Data capture, analysis, investigation and dissemination
- The most advanced imaging solution available
- An easy-to-use interface
- Five built-in, fast and thorough search engines
- Built-in development environment
- Built-in file viewers for hundreds of file types
- The leading salvage engine
- Extremely fast hash engines and automated data reduction techniques
- Built-in e-mail store processing, searching and viewing
- Filesystem, file and e-mail recovery
- Multiple categorization features
- Registry viewing and searching
- Virus/Trojan search and identification
- VMware virtual disk production from devices or images
- Context dictionary production for password cracking
- IVault data store preparation and production
- Support for all common archive file formats
- Deconstruction of evidentially useful file types
- Sorting, grouping and filtering of files and e-mail.
- Advanced analysis functions
- Advanced MS Outlook e-mail recovery
- Password protected file detection
What Our Customers Are Saying:
"...And you make take pride in knowing that ILook worked like a charm, whereas [the other software] was crashing multiple times for a lot of people. They weren't too happy."
- Federal Computer
Elevate Current User to SQL Server Admin
If you fail to make your user Administrator in SQL Server, you must use this guide in order to elevate yourself to the Administrator permission level. You must run SQL Server Management Studio and through that, change your login , at the server roles, permissions level. It is a simple checkbox selection to add the permission to the Current Roles.
Additional Microsoft Notes:
On Windows XP, SQL Server installs with the BUILTIN\Administrators group as the default system administration group.
On Windows Vista, users that are members of the Windows Administrators group are not automatically granted permission to connect to SQL Server, and they are not automatically granted SQL Server administrator privileges. When they try to connect to SQL Server, a message is returned that states that the account does not have rights to log in to SQL Server.
Note: In SQL Server Express, Windows users are granted connect permission because the BUILTIN\Users group is provided as a login.
When a user in the Administrators account runs SQL Server Management Studio, the User Account Control feature strips the membership token for that group and passes only the user account information to SQL Server. A message is returned that states that the account does not have rights to log in to SQL Server. To let members of the Windows Vista Administrators group log in, you must explicitly add the account to the SQL Server logins.
To add a Windows user that has the login “domainname \username” or “machinename\Administrator” to the sysadmin fixed server role
1. Log on to the computer using the credentials for the domainname\username account.
2. Click the Start button, point to All Programs, click Microsoft SQL Server, right-click SQL Server Management Studio, and then click Run as administrator.
Note: The Run as administrator option elevates the user permissions.
3. In the User Access Control dialog box, click Continue.
4. Follow the 5 steps in the below screen to add the permission level for server admin to the instance installation if it is not already added.