Adventure Time Finn and Jake Investigations

Adventure Time Finn and Jake Investigations.zip

creating a scheduled task running as system

Again, this is not a SharePoint post per se, but hey, we all need to Schedule a task from time to time, unless we have completely flown into the clouds…

No need for any command prompt, at.exe, schtasks.exe or anything like that. This can all be done from the gui.

Note: Some people may state that it is a bad idea running a scheduled task as system, that this is bad for security reasons. I can agree with both sides but a fact is that Microsoft has a number of their default scheduled tasks running as system, so it can’t all be wrong. Also, running the task as a different administrator account is even worse, so…do as you like here. Secure the location of the script files, at least do that. Good or bad, it is still a fact that some people in some situations want to do this, run a script as system, perhaps for the simplicity of it, for not having to rely on service accounts beeing created or other reasons good or bad.

Step by step:

Note: These steps have been verified on Windows Server 2012, but will function just as well on Windows Server 2012 R2 or Windows Server 2008R2/Windows Server 2008, Windows 7 nd Windows 8x

-

Note: You have to be logged on as a local administrator in order to follow these steps.

Start the Windows Task Scheduler, from the ‘Start’ menu or search, any way works…
When the Windows Task Scheduler is open, Browse to a task under Microsoft. I’m using a .NET Framework task in my example, that will work…

Have a look at the tasks in the .NET Framework container. Select the task at the top and make sure that it is a task running as System by checking its properties.

The properties at the bottom will show you if the task is configured to run as SYSTEM. If the task selected is not, pick another task in the list until you find one that is.

Right-click on the task and select export.

Save the file to a good location locally on the server and give it a good name.

Replace the default name with something of your own:

Save the file, then back in Task Scheduler, select the top of the tree, Task Scheduler Library.

Right-click on Task Scheduler Library and select Import Task…

Browse to the file you just exported.

Click on Open to start the import of the task. Name the new task with the name you want, you now have an exact copy of the default .NET framework task, now we need to make modifications so that it will suit your needs.
Right-click on the task, select Properties to make all the settings available for change.
In my example, I want the task to start a PowerShell script as system.
In order to do that, go to the Actions tab.

Delete the existing action, in my example ‘Custom handler’ and add your own.

If you like me, want to run a PowerShell script, type powershell in the program field and type the path to your .ps1 file in the Add Arguments field.
Save the new action and verify the values.

Now, change all the parameters to suit your needs. For example, you might want to add a scheduled trigger.
Click on the Triggers tab and add the Schedule you need.

In my example, I added a Schedule that starts the task at 07:00 every day and keeps doing this forever…

Now, as a last step, select the completed task under the Task Scheduler Library and verify all the settings, especially, make sure that it is configured to run as SYSTEM!
I also selected Run with highest privilieges in my example because the script I had writted required Run as Administrator to function properly.

Thats all, you’re done! Good luck!

How to enable Ping in Windows Server 2012

This is just a quick guide to enabling a server to respond to ping, the default setting in Windows Server 2012 is to not respond. This is how you do it:

The exact same steps apply to Windows Server 2012 R2

-
GUI – Graphical User Interface
1. Open Control Panel, then select System and Security by clicking on that header

-
-
2. Select Windows Firewall

-
-
3. Advanced Settings

-
-
4. In ‘Windows Firewall with Advanced security’ click on ‘Inbound rules’

-
-
5. Scroll down to ‘File and Printer sharing (Echo request – ICMPv4-In)

-
-
6. Rightclick on the rule and select ‘Enable rule’

-
-
Make sure that it turns green

Done, close down the ‘Windows Firewall with Advanced Security’ windows and then the Control panel.
Verify functionality by pinging the servers own IP address from a command or PowerShell prompt.
Done!

-
-
PowerShell
(This will enable the existing rule exactly as the instruction above does)

Import-Module NetSecurity
Set-NetFirewallRule -DisplayName “File and Printer Sharing (Echo Request – ICMPv4-In)” -enabled True

 

(ABove enables the existing rule, below will create a new rule that allows ICMPv4/Ping and enable it)

Import-Module NetSecurity
New-NetFirewallRule -Name Allow_Ping -DisplayName “Allow Ping”  -Description “Packet Internet Groper ICMPv4″ -Protocol ICMPv4 -IcmpType 8 -Enabled True -Profile Any -Action Allow

 

(For IPv6 Ping you obviously enable the v6 Inbound Rule…)
Thats all there is to it!