Advanced Windows PowerShell Scripting Video Training

Advanced Windows PowerShell Scripting Video Training
Advanced Windows PowerShell Scripting Video Training

Friday, July 30, 2010

Control how often a warning message is sent to users in Exchange 2010

By default, Exchange 2010 sends a warning email to all users every day at 1:00 AM. In the past, I’ve often needed users to be more aware of their utilization. Especially if we were approaching storage capacities. You can create a custom schedule to send more notices throughout the day if needed.
· Open the Exchange Management Console.
· Expand Organization Configuration.
· Click Mailbox.
· Right click the database you want to configure and select Properties.
· Click the Limits tab
· Click Customize
· Configure your notification schedule and then click OK.
· In the drop down box, click Use Custom Schedule.
· Click OK.
To configure the notification schedule with PowerShell by using the –QuotaNotificationSchedule switch with the Set-MailboxDatabase cmdlet. Here is an example
Set-MailboxDatabase –identity “” –QuotaNotificationSchedule “Mon.9:00-Mon.10:00”, “Wed.9:00-Wed.10:00”
The above command will send a notification to all users who need one on both Monday and Wednesday between the hours of 9:00 AM and 10:00 AM.

Wednesday, July 28, 2010

How to program in your wireless access points to your clients.

In class is gave the wrong information about how to set your access points up on your clients. The Connection Manager Administration Kit is not the correct answer. There is a GPO setting for this.

· Open or create a new GPO.

· Expand Computer Configuration à Policies à Windows Settings à Security Settings à Wireless Networks (IEEE 802.11) Policies.

· Right click Wireless Networks (IEEE 802.11) Policies and select Create a New Wireless Network Policy for Windows Vista and Later Releases.

· Provide a Policy Name and a Description

· Click Add à Infrastructure.

· You can now add the SSID, Authentication, and Encryption type for each of the wireless access points in your organization.

Monday, July 26, 2010

Connection Manager Administration Kit

The connection Manager Administration Kit (CMAK) allows you to send configuration information to your users to set up a VPN connection for them. CMAK will create a profile with all the required settings. The user simples opens the file you send them and all the work is done. Click the following link for more information from Microsoft.

http://technet.microsoft.com/en-us/library/cc753977(WS.10).aspx

Friday, July 23, 2010

How to manage multiple local group policies in Windows 7

First off, I recommend against using Local Policies in a domain environment. One of the reasons for using Group Policies is the one-to-many administration that you get. Should you utilize local policies, you will have to visit each client manually.

Local Policies should only be used in a work group environment of 10 or less clients.

Here is how you manage them.
• Click Start
• Type MMC and press Enter.
• Click File and then Add/Remove Snap-in…
• Select Group Policy Object and click Add.

At this point, we can decide wheich of the policies we want to configure.
• Click Browse.
• Click the Users tab.

You can now choose to modify the local policy for a specific user, users who have local administrator rights, or users who do not have local administrator rights.
• Click OK and then Finish

When a user logs on to this client, the appropriate local policy will be applied.

Wednesday, July 21, 2010

How to get a list of all the configured values in a GPO

One of the challenges that one of you mentioned was the difficulty in enumerating the settings in a GPO in a convenient way. Below is a procedure to try one your Windows Server 2008 R2 domain controllers. It uses PowerShell to extract the data for you.
· Log in to the DC.
· Click Start à Windows PowerShell Modules.
· Type Get-GPOReport –Name NameOfGPO –ReportType HTML –Path Destination and file name.
Open the HTML file that was generated. The only values in the policy that are shown are the values that have been set. Also, if the name of your GPO has a space in it, enclose the name in double quotes. Below is an example of a policy that configured WSUS.

Links
Location
Enforced
Link Status
Path
None

This list only includes links in the domain of the GPO.
Security Filtering
The settings in this GPO can only apply to the following groups, users, and computers:
Name
NT AUTHORITY\Authenticated Users
Delegation
These groups and users have the specified permission for this GPO
Name
Allowed Permissions
Inherited
MCTNET\Domain Admins
Edit settings, delete, modify security
No
MCTNET\Enterprise Admins
Edit settings, delete, modify security
No
NT AUTHORITY\Authenticated Users
Read (from Security Filtering)
No
NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS
Read
No
NT AUTHORITY\SYSTEM
Edit settings, delete, modify security
No
Computer Configuration (Enabled)
Policies
Administrative Templates
Policy definitions (ADMX files) retrieved from the local machine.
Windows Components/Windows Update
Policy
Setting
Comment
Enabled
Check for updates at the following
interval (hours):
4
Policy
Setting
Comment

This setting lets you specify if automatic updates are enabled on this computer. If the service is enabled, you must select one of the four options in the Group Policy Setting:

2 = Notify before downloading any updates and notify again before installing them.

When Windows finds updates that apply to this computer, an icon appears in the status area with a message that updates are ready to be downloaded. Clicking the icon or message provides the option to select the specific updates to download. Windows then downloads the selected updates in the background. When the download is complete, the icon appears in the status area again, with notification that the updates are ready to be installed. Clicking the icon or message provides the option to select which updates to install.

3 = (Default setting) Download the updates automatically and notify when they are ready to be installed

Windows finds updates that apply to your computer and downloads these updates in the background (the user is not notified or interrupted during this process). When the download is complete, the icon appears in the status area, with notification that the updates are ready to be installed. Clicking the icon or message provides the option to select which updates to install.

4 = Automatically download updates and install them on the schedule specified below

Specify the schedule using the options in the Group Policy Setting. If no schedule is specified, the default schedule for all installations will be everyday at 3:00 AM. If any of the updates require a restart to complete the installation, Windows will restart the computer automatically. (If a user is logged on to the computer when Windows is ready to restart, the user will be notified and given the option to delay the restart.)

5 = Allow local administrators to select the configuration mode that Automatic Updates should notify and install updates

With this option, the local administrators will be allowed to use the Automatic Updates control panel to select a configuration option of their choice. For example they can choose their own scheduled installation time. Local administrators will not be allowed to disable Automatic Updates' configuration.

To use this setting, click Enabled, and then select one of the options (2, 3, 4 or 5). If you select 4, you can set a recurring schedule (if no schedule is specified, all installations will occur everyday at 3:00 AM).

If the status is set to Enabled, Windows recognizes when this computer is online and uses its Internet connection to search Windows Update for updates that apply to this computer.

If the status is set to Disabled, any updates that are available on Windows Update must be downloaded and installed manually. To do this, go to http://windowsupdate.microsoft.com or click Start, click Programs (or click All Programs), and then click Windows Update.

If the status is set to Not Configured, use of Automatic Updates is not specified at the Group Policy level. However, an administrator can still configure Automatic Updates through Control Panel." gpmc_supported="At least Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 1" style="cursor:pointer">Configure Automatic Updates
Enabled
Configure automatic updating:
3 - Auto download and notify for install
The following settings are only required
and applicable if 4 is selected.
Scheduled install day:
0 - Every day
Scheduled install time:
06:00
Policy
Setting
Comment
Enabled
Wait after system
startup (minutes):
10
Policy
Setting
Comment
Enabled
Set the intranet update service for detecting updates:
http://MCT1
Set the intranet statistics server:
http://MCT1
(example: http://IntranetUpd01)
User Configuration (Enabled)
No settings defined.
Reference:

Monday, July 19, 2010

Can RMS run on Windows XP?

AD RMS (Rights Management Services), allows your users to designate who can do what with the content they create from Rights aware applications. For example, who can read a document and who can print it. This is done without IT staff making any changes to NTFS file permission. AD RMS works with Windows Vista, Windows 7, and Windows Server 2008. You can also utilize AD RMS with Windows XP, 2000, 2003. To do this, you wil need to download a separate version from Microsoft. The following link will direct you to the correct download for your platform: http://technet.microsoft.com/en-us/library/cc731051.aspx.

Friday, July 16, 2010

List of supported Operating Systems for Hyper-V R2

Supported Server Operating Systems

The following server operating systems are supported on Hyper-V:

  • Windows Server 2008 R2 Standard

  • Windows Server 2008 R2 Enterprise

  • Windows Server 2008 R2 Datacenter

  • Windows Web Server R2 2008

  • Windows Server 2008 Standard x64

  • Windows Server 2008 Enterprise x64

  • Windows Server 2008 Datacenter x64

  • Windows Web Server 2008 x64

  • Windows Server 2008 HPC Edition x64

  • Windows Server 2008 Standard without Hyper-V x64

  • Windows Server 2008 Enterprise without Hyper-V x64

  • Windows Server 2008 Datacenter without Hyper-V x64

  • Windows Server 2008 Standard x86

  • Windows Server 2008 Enterprise x86

  • Windows Server 2008 Datacenter x86

  • Windows Web Server 2008 x86

  • Windows Server 2008 HPC Edition x86

  • Windows Server 2008 Standard without Hyper-V x86

  • Windows Server 2008 Enterprise without Hyper-V x86

  • Windows Server 2008 Datacenter without Hyper-V x86

  • Windows Server 2003 Standard x86 Edition with Service Pack 2

  • Windows Server 2003 Enterprise x86 Edition with Service Pack 2

  • Windows Server 2003 Datacenter x86 Edition with Service Pack 2

  • Windows Server 2003 Web x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Standard x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Enterprise x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Datacenter x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Web x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Standard x64 Edition with Service Pack 2

  • Windows Server 2003 R2 Enterprise x64 Edition with Service Pack 2

  • Windows Server 2003 R2 Datacenter x64 Edition with Service Pack 2

  • Windows Server 2003 Standard x64 Edition with Service Pack 2

  • Windows Server 2003 Enterprise x64 Edition with Service Pack 2

  • Windows Server 2003 Datacenter x64 Edition with Service Pack 2

  • Windows 2000 Server with Service Pack 4

  • Windows 2000 Advanced Server with Service Pack 4

  • SUSE Linux Enterprise Server 10 with Service Pack 1 (x86 Edition or x64 Edition)

  • SUSE Linux Enterprise Server 10 with Service Pack 2 (x86 Edition or x64 Edition)

  • SUSE Linux Enterprise Server 11 (x86 Edition or x64 Edition)

  • Red Hat Enterprise Linux (RHEL) 5.2, 5.3 and 5.4 (x86 Edition or x64 Edition)

Supported Client Operating Systems

The following client operating systems are supported on Hyper-V:

  • Windows 7 Professional x86 Edition

  • Windows 7 Enterprise x86 Edition

  • Windows 7 Ultimate x86 Edition

  • Windows 7 Professional x64 Edition

  • Windows 7 Enterprise x64 Edition

  • Windows 7 Ultimate x64 Edition

  • Windows Vista Business x86 Edition with Service Pack 1

  • Windows Vista Enterprise x86 Edition with Service Pack 1

  • Windows Vista Ultimate x86 Edition with Service Pack 1

  • Windows Vista Business x64 Edition with Service Pack 1

  • Windows Vista Enterprise x64 Edition with Service Pack 1

  • Windows Vista Ultimate x64 Edition with Service Pack 1

  • Windows XP Professional x86 Edition with Service Pack 3 (VMs configured with 1 or 2 virtual processors)

  • Windows XP Professional x86 Edition with Service Pack 2 (VMs configured with 1 virtual processor)

Windows XP Professional x64 with Service Pack 2 (VMs configured with 1 or 2 virtual processors)


http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx