1) From the run command (Windows + r) enter the command "control userpasswords2" (without quotes).

2) This will open the "User Accounts" window, select the Advanced Tab on the top.

3) At the bottom of the window there will be a check box that says "Require users to press Ctrl+Alt+Delete"

4) Uncheck this box and click the apply button then the OK button.

5) You are now complete

My coworker wrote a script in PowerShell to automate the scheduling of incremental crawls, being there were more than 80 of them to set up. When he was using the "CrawlScheduleDaysofWeek" parameter he found that the days of week were based on numbers and not names (makes sense right?).

In our attempts to dissect how the days where numbered we output and found that Sunday equaled 1, great . . . so now Monday equaled 2 . . . now we are getting some where. But the problem was Tuesday does not equal 3 it actually equals 4.

Let me explain why, in our coding background we found that for VB, C#, Java the "daysofweek" parameter is consistent in format no matter the language. The PowerShell team has taken this common format and applied it to the SharePoint PowerShell, which is great. Now we know that PowerShell has the same roots as other programming languages (or at least tries to stick with what people are already used too).

Below is the table (and for those of you yes it is a binary based format)

Here is the table for days of week number equivalent:

So in order to get the right days of week simply add the numbers up and they will equal the days of week you want checked. In our case we wanted everyday but Tuesday to be checked for incremental crawls. We simply took all the days number equivelants and added them together minus Tuesday (127 - 4) which equaled 123. When the script was ran it set up the schedule for Sunday thru Saturday and excluded Tuesdays checkbox in the SharePoint Crawl UI. Perfect.

Hope this helps everyone.

 Some associated links that were used to put this together:

https://msdn.microsoft.com/en-us/library/microsoft.windowsmobile.pocketoutlook.daysofweek.aspx

https://technet.microsoft.com/en-us/library/ff607675.aspx

To open the "Ease of Access Center" press: Windows logo key + U

Under "Explore All Settings", select: "Use the computer without a display" by pressing TAB, then ENTER

Under "Adjust time limits and flashing visuals", select: the drop down box and select the time you want (the interval is between 5 Seconds to 5 Minutes).

This article is not intended to resolve your issue, more assist in some common issues found when installing the prerequisite. First and foremost, the server your trying to install SP2010 on has to be able to get to the Internet (Out to see the wonderful WWW).

Second (this was found by a collegue (Clinton Schneider)), he found that if you have not run the initial configuration wizard for IE8 (this is on Server 2008 R2 if you are wondering) the setup fails, the server is getting onto the web to grab Geneva (and some other bits) in order for the reprequisite installer to function.

Last but not least, please make sure that the account or user has administrative permissions to install applications and features on the server.

Big thanks to Clinton.

To open the editor simply open a run* command and type EUDCEDIT (End User Defined Characters Editor)

This is a hexidecimal based editor, once the code base is selected you will get the actual editor, think of this as a mini-paint tool. The functionality is limited, but the abilities to application of custom icons are endless. From Outlook signatures to favicon's this highly functional tool is worth your time.

* if you cannot see a run command button on your windows menu please follow the below steps (Windows 7):

Right Click your Windows menu button > select "Start Menu" tab > left click on the "Customize" button > approx. 3/4 of the way down is the check box titled "Run command" put a "Check" in the box > Click OK > OK

Netstat -an | find ":80" /c

This will output only the number of current connections.

The parameter ":80" is the port number if your site is SSL only and standard change the ":80" to ":443".

Remember if you monitoring your website that counts as at least one connection. . .

Query Session Server:%ServerName%

The output you receive will look like this:

SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
services                                                       0  Disc                                    
rdp-tcp#0         %username%                        1  Active  rdpwd                       
console                                                       3  Conn

Now you can then determine from the screen above what session can be logged off (as long as you are an administrator on the machine). I always ask if I can log them off before doing so, they might be running a long task. To log someone off of their remote session simply configure the command below using the ID # and Session Name above:

logoff [{SessionID | SessionName}] [/server:ServerName] [/v]

During administration days when the family is watching cable TV I use TS to administer the machine (being that the monitor is the TV and being used). I reboot the machine using an icon on my desktop that is simple and quick.

On your desktop right-click and choose "New-Shortcut" your location will be an old DOS command with parameters you determine. Copy and Paste this command:

Shutdown -r -t 120

Enter the above, then click next, provide a name and click the finish button. What this command states is "Shutdown" this computer - with restart "-r" - after 120 seconds"-t 120". You can right click then select properties and "Change Icon" to anything you want.

The "Shutdown" command has been around since the beginning of time (well at least in my mind). There are many things you can do with the Shutdown command, to enter the help menu to create your own shutdown methods use shutdown /?. I suggest you create a stop shutdown icon right next to this one just in case you ever click on it by accident. To stop a shutdown procedure simply create another shortcutwith the following command:

Shutdown -a

This will stop any current shutdown; I got really familiar with this command with the blaster worm.

* On a side note if you don’t want to go about creating icon's, or not even having to log into the machine and you wish to reboot a machine (or a hundred), open a command prompt type shutdown -r -m \\%machinename% -t 120 this will restart a remote computer (as long as you are an administrator of that machine). And No, you can’t reboot your co-workers machine without having administrative permissions (Trust me on this one).

Install PowerShell 2.0 if you don't already have it installed on your system.

Create a common folder where you can put your PowerShell files (Mine is D:\PowerShell). Create a text file"%nameoffile%.ps1" you can name it whatever you want it doesn't matter since you will be referencing it directly. (I do recommend naming it something descriptive, when you get hundreds of files they are easier to manage).

Open the text file and enter the following text:

## speed.msh

## Kill!

foreach ($strComputer in $Args)

{

            $adapters = get-wmiobject -query "Select MACAddress, Caption From Win32_NetworkAdapterConfiguration Where DatabasePath IS NOT NULL" -namespace "root\cimv2" -computername $strComputer

            foreach ($adapter in $adapters)

            {

                        $mac = $adapter.MACAddress

                        $adapterName =  $adapter.Caption.substring(11)

                        $linkSpeedObj = get-wmiobject -query "Select NdisLinkSpeed From MSNdis_LinkSpeed Where InstanceName = '$adapterName'" -namespace "root\wmi" -computername $strComputer

                        $adapterObj = get-wmiobject -query "Select NetConnectionID From Win32_NetworkAdapter Where MACAddress = '$mac'" -namespace "root\cimv2" -computername $strComputer

                        $result = $strComputer.ToUpper() + ", " + $adapterObj.NetConnectionID + ", " + $linkSpeedObj.NdisLinkSpeed

                        write-host $result

            }

}

Open your PowerShell interface, after the window opens be sure to set you execution policy to unrestricted ("Set-ExecutionPolicy Unrestricted") then after reading the disclaimer select your option. [?] the help feature does provide useful information about remote execution exposures. After entering "Y" you will proceed to an unrestricted execution line.

Change the directory path to the the folder where you are keeping your files. In our case d:, then cd .\PowerShell, once you are in the directory you can start with the execution portion of the query.

The command has the ability to output more than just single server results. Just enter the file name then a "space" then the server name "space" server name, ect. . . see details below.

PS D:\PowerShell> %nameoffile%.ps1 %servername% %servername%

The output is simple and readable. If you have multiple network adapters it will output the names of each network adapter also. The output will look like "

"%Servername%, EFL, 1000000"

Brief walkthrough:

Start by opening your run command, and type iExpress (Start > Run > iExpress) this will open a small window giving you two options.

"Create new Self Extraction Directive file" or "Open existing Self Extraction Directive file" the second option gives you a browse button to find an existing package (.SED)so you can add or subtract components from the .exe.

 In this example we will select "Create new . . ." then click "Next >" you will find three different options here that will give you a short description of what they do at the bottom in a dialog box. Let us select the "Extract files only" option and click "Next >". Type in the name that you want the package description to say in our case "Isaac's Pictures" then click "Next >".

In our next option it gives us two choices "No Prompt." or "Prompt user with:" we use this option to confirm to the user that they will be decompressing the package and placing it in a destination of their choosing. In our case I have chosen to prompt the user with "Extract Isaac's Pictures?" they will receive a dialog box with a Yes or No option. Click "Next >" this next dialog box allows you to manufacture or use an existing license agreement, giving you the ability to limit liability and such, if necessary . . . we have elected to select the "Do not display a license."

The next box gives you the "Add" and "Remove" buttons which allows you to add either a single or multiple files to this executable. Once you have completed with entering the contents of the package click "Next >".

 The "Show Window" options gives you the ability to install/extract your folder/application and run it in any option you choose, from hidden to maximum window. It is entirely up to you how you want your installation/extraction to be perceived by the consumer of your .exe. The Finish message is a nice ending especially when you have chosen to hide your installation progress; this gives you the ability to enter a custom display message other than "Installation Complete". I use the custom finish button as a special touch when sending photos or documents to family members.

The last option asks you where you would like your files to be placed in the consumers directories, it also gives you options to hide the extraction status bar and whether or not you want to store Long File names inside the package. I selected the location C:\users\public\desktop and unchecked both boxes for hidden and long file names.

Then you have the option of saving your configuration settings as a “.SED” file which gives you the ability to edit the current configuration and add/subtract files later. I don’t usually do this unless I know we will be using the exact configuration again.

Now we click create package, this will create the “.exe” that you can send out to consumers or friends/family.