|
|
|
| |
| 29 | 30 | 31 | 1 | 2 | 3 | 4 | | 5 | 6 | 7 | 8 | 9 | 10 | 11 | | 12 | 13 | 14 | 15 | 16 | 17 | 18 | | 19 | 20 | 21 | 22 | 23 | 24 | 25 | | 26 | 27 | 28 | 29 | 30 | 1 | 2 | | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
|
"Reboot required check failed" when you intalling SQL 2008 Server or SQL 2008 Server Service Pack 1 (SP1)
|
|
When you intalling SQL 2008 Server or SP1 you receive the following error message: "Reboot required check failed".
Resolution:
The fix for this issue start RegEdit.exe, point to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager and navigate to PendingFileRenameOperations.
Remove any data assocuated with the value and rerun installation.
|
|
|
Microsoft Small Business Server 2008 Roaming Profiles & Redirected Folders? How? To Another Server?
|
|
In Microsoft Small Business Server 2008 ( SBS 2008 ), you can configure the redirect the Desktop, Documents, Start Menu folder for users simply in the SBS console.
To do that:
1. In the SBS 2008 console, click the Users and Groups tab.
2. In the task menu, click the "Redirect folders for user accounts to the
server" to open the wizard.
3. Choose the folder(s) you want to redirect and finish the wizard.
If you are in the process of migrating Small Business Server 2003 to Small Business Server 2008, you may refer to the following link to move data to the new SBS 2008 Server.
By default all redirected folders are stored in
\\SBS\Redirectedfolders\%username% folder. To redirect the folder on a
secondary server, you may need to manually change the path in the SBS
Folder Redirection policy.
For those existing redirected folder on the SBS server, you can simply move
the user's redirected folders to a secondary server with the Move User's
Redirected Documents Data wizard. To do that:
1. In the Small Business Server 2008 console, click the Backup and Server Storage tab.
2. In the task menu, click the Move User's Redirected Documents Data to
open the wizard.
3. Finish the wizard to move the folders.
|
|
|
|
|
Creating Strong Passwords
|
|
While security has never been more important than it is today, the fastest way for an IT professional to become the most despised person in the company is to start enforcing a strong password policy. A policy perceived as overbearing may cause people to write down their passwords on a sticky note near their computers, circumventing its very purpose. Your policy will be ineffective if your users don't know how to create strong passwords that are easy to remember.
Left to their own devices, people will choose passwords that are simple for them to remember. They'll use their spouse's name, their dog's name, their favorite sports team or a recent vacation spot. Sometimes while working on a user's computer, I'll need to log on as that person after a reboot. Unfortunately, he's wandered off, not wanting to hover over the IT guy. I generally prefer not to know other people's passwords, so I usually don't ask. In this situation, I sometimes take a guess. I've been right a surprising number of times, and sometimes with people who are very powerful. It's easy. I simply glance around their offices and note what their obsessions are.
Keys to password strength: length and complexity
An ideal password is long and has letters, punctuation, symbols, and numbers.
- Whenever possible, use at least 14 characters or more.
- The greater the variety of characters in your password, the better.
- Use the entire keyboard, not just the letters and characters you use or see most often.
Create a strong password you can remember
There are many ways to create a long, complex password. Here is one way that may make remembering it easier:
| Start with a sentence or two (about 10 words total). |
Think of something meaningful to you. |
Long and complex passwords are safest. I keep mine secret. (10 words) |
| Turn your sentences into a row of letters. |
Use the first letter of each word. |
lacpasikms (10 characters) |
| Add complexity. |
Make only the letters in the first half of the alphabet uppercase. |
lACpAsIKMs (10 characters) |
| Add length with numbers. |
Put two numbers that are meaningful to you between the two sentences. |
lACpAs56IKMs (12 characters) |
| Add length with punctuation. |
Put a punctuation mark at the beginning. |
?lACpAs56IKMs (13 characters) |
| Add length with symbols. |
Put a symbol at the end. |
?lACpAs56IKMs" (14 characters) |
By using the following tips, people will be able to create easy-to-remember passwords that follow these typical requirements: at least eight characters long and with at least three of the following character types: uppercase letters, lowercase letters, numbers and special characters:
-
Substitute numbers for letters and vice versa. (o instead of 0, 4 instead of A, 1 instead of L, E instead of 3)
-
Substitute words for numbers (one, two, three ... )
-
Combine both of the above (0ne, thr33, f1ve)
-
Use capitalization in random places (bLue, happY)
-
Use special characters ( !@#$%^&*(){}[] ) to punctuate and separate words
-
Create passwords out of words, numbers or phrases you'll remember
-
Misspell words
Using these tips, you can create memorable passwords that will be nearly impossible to guess. Here are some examples of converting memorable information into a complex password
We'll start with some easy ones:
More complex passwords:
-
19 Peach Place becomes: 0ne9peacHpl!
-
I love Jill becomes: eYelov3Jill
-
My dog Fritz becomes MeyedogfrltZ
Common password pitfalls to avoid:
Cyber criminals use sophisticated tools that can rapidly decipher passwords.
Avoid creating passwords using:
- Dictionary words in any language.
Words in all languages are vulnerable.
- Words spelled backwards, common misspellings, and abbreviations.
Words in all languages are vulnerable.
- Sequences or repeated characters.
Examples: 12345678, 222222, abcdefg, or adjacent letters on your keyboard (qwerty).
- Personal information.
Your name, birthday, driver's license, passport number, or similar information.
Substitute numbers for letters and vice versa. (o instead of 0, 4 instead of A, 1 instead of L, E instead of 3)Substitute words for numbers (one, two, three ... )Combine both of the above (0ne, thr33, f1ve)Use capitalization in random places (bLue, happY)Use special characters ( !@#$%^&*(){}[] ) to punctuate and separate wordsCreate passwords out of words, numbers or phrases you'll rememberMisspell wordsFriday becomes frYday!Robert becomes #robERt#867-5309 becomes 8siX753o919 Peach Place becomes: 0ne9peacHpl!I love Jill becomes: eYelov3JillMy dog Fritz becomes MeyedogfrltZ
|
|
|
The values of the datetime column are not same for the rows that are copied when you copy data to a table by using the GETDATE() function in Microsoft SQL Server 2005
|
When you copy data to a table that contains a column of the datetime data type in Microsoft SQL Server 2005, the values of the datetime column are not same for the rows that are copied. This issue occurs if you copy all the rows in one batch or if you copy rows in batches by specifying a batch size.
Note This issue does not occur in SQL Server 2000 or in SQL Server 2008.
This issue may occur in one of the following scenarios. Scenario 1
You set the default value of the datetime column to the GETDATE() function. You bulk copy data between the table and a data file by using the BUIL INSERT statement or by using the Bulk Copy Program (BCP) utility. When you copy data, you do not specify values for the datetime column in the data file.
Scenario 2
You copy data by using a distributed query that uses the GETDATE() function to set values for the datetime column.
RESOLUTION
The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
956854Â (http://kbalertz.com/Feedback.aspx?kbNumber=956854/ ) Cumulative update package 10 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137Â (http://kbalertz.com/Feedback.aspx?kbNumber=937137/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack. |
|
 
|