1. First connect to Office 365 via PowerShell more on this here. Consider, you need administration privileges to change account settings for other users..
2. To get a list of the Microsoft Online Office 365 users:

   Get-MsolUser

   

3. To get the details for a user:

   Get-MsolUser -UserPrincipalName user.name@domain.xy

   

4. Now you can use the following cmdlet to change the password policy for the password to never expire..

   Set-MsolUser –UserPrincipalName user@contoso.com –PasswordNeverExpires $true

5. and if you’re a freak like me

   Get-MsolUser | Set-MsolUser -PasswordNeverExpires $true

   

   That will change the password policy for all users – have phun!

1. Install the Microsoft Online Services Sign-In Assistant
   32-bit
   64-bit
2. Install the Microsoft Online Services Module for Windows PowerShell
   32-bit
   64-bit
3. Open PowerShell and import the MsOnline Module or use the desktop shortcut which was created by the installer.

   
   

   
   Import—Module MsOnline

   

4. Connect to your Microsoft Office 365 account

   Connect-MsolService

   

   Use your Office 365 LiveID to login (for example username@company.onmicrosoft.com)

5. Now you can start working with Windows Powershell in your Office 365 account, if you need some more help about the available Powershell cmdlets you can list them with

   Get-Command –Module MsOnline

   

have phun!

When I checked the Device Manager using devmgmt.msc I realized, that there was this unknown device which prevents me and my mouse to communicate with my computer. Well, there must be a driver on the supplied CD, now?. I installed SetPoint (I hate it to install unnecessary software on my systems..!) but the missing driver was not part of the SetPoint Installer/Software. I realized, that the software on the CD was dated back to 2009. I started a browser and navigated to http://www.logitech.ch downloaded the latest version (6.32) of SetPoint for Windows 7 64bit and installed it on my system. Still no luck. Finally I found page where a user complained about the same issue ..

http://forums.techarena.in/hardware-peripherals/1446885.htm

The steps I’ve take that solved the problem were:

• You have to go for following location C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_e2b28ecac19a29af’.
• Now copy usb.inf and usb.PNF to the ‘C:\Windows\INF\’ location.
• After that you will need to update the drive which is as a unknown devices.
• Now launch the Device Manager and Right click on it and go for Properties.
• Choose Driver and click on the Update Drive.
• Once done select Browse my computer for driver software and enter ‘C:\Windows\INF\’ into the Search for the driver software and click on Next.

Well, the directory usb.inf_amd64_neutral_xxxxx was not listed under C:\Windows\System32\DriverStore\FileRepository but there were to other similar directories: usb.inf_amd64_neutral_153b489118ee37b8 and usb.inf_amd64_neutral_269d7150439b3372 I copied both to C:\Windows\inf and changed back to Device Manager. Right-Mouse-Click on the Unknown Device, Update Driver then Browse and select C:\Windows\Inf. Now the System warned me about an unsigned driver. what I ignored. Boom the USB Receiver was recognized and the mouse was and is working!

See this post as a summary of what I’ve learned when analyzing Windows Error Reporting feature and it’s ‘shortcomings’

Years ago Microsoft started with fault-detection creating Dr. Watson. Dr. Watson evolved during the last years to a complete Error Reporting feature called Windows Error Reporting. The feature consists of a Windows Service called Windows Error Reporting Service

C:\>sc query WerSvc

SERVICE_NAME: WerSvc
        TYPE               : 20  WIN32_SHARE_PROCESS
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0×0)
        SERVICE_EXIT_CODE  : 0  (0×0)
        CHECKPOINT         : 0×0
        WAIT_HINT          : 0×0

C:\>services.msc

Additionally there are a few DLLs which can be found in %WinDir%\System32 / %WinDir%\SysWow64.

The Windows Error Reporting feature, respectively WerFault.exe gets triggered if an application terminates unexpectedly. You can change the behavior of the Windows Error Reporting feature using various Windows registry keys:

Here’s an example dialog in Win7 with the usual settings:

If you disable the AeDebug registry key, the JIT debugging option goes away:

If you disable checking for solutions (the only thing you seem to have control over via the control panel), it looks like this, but still appears and still stops the program from dying until the user presses something.WerAddExcludedApplication is documented to also have this effect.

Windows Error Reporting can be configured using GPOs:

Start gpedit.msc, go to Computer Configuration – Administrative Tools – Windows Components – Windows Error Reporting

There you can change/control the behavior of WER.

If you don’t change the configuration of Windows Error Reporting, a crash dump is being written to %ProgramData%\Microsoft\Windows\WER

There you can find a Reporting Queue and a Report Archive:

so far the whole WER feature works good and does not make any problems. BUT, if you change startup type of the Windows Error Reporting Service to Disabled,  Windows Error Reporting begins to make problems. If you do so, and a program triggers WerFault.exe, the WerFault.exe Process won’t terminate until you kill it yourself using taskkill /IM werfault.exe or taskmanager. This happens because WerFault.exe tries to start the Windows Error Reporting Service. Since WER Service is disabled and cannot be startet, WerFault.exe remains/hangs…. This is a big shortcoming of WER. Because: imagine you have a windows service which crashes, Werfault.exe is beeing triggered, the crashing process (windows service) can not terminate until werfault.exe reports the fault. you won’t be able to restart the windows service in some ‘constellations’.

we have escalated this to Microsoft Support. They provided us with the solution of preventing WerFault.exe from being run using Image File Execution.. I’m absolutely not a fan of this ‘solution’ it’s more of a workaround..

Resolution

If you need to ensure that Werfault.exe will never be spawned when an unhandled exception is encountered, you can choose one of the following resolution paths.

1) Create a software restriction policy (via local policy or Domain GPO) to disallow Werfault.exe for all users.

Or

2) Use Image File Executions Options to cause Werfault.exe to be executed under a non-existent debugger(NUL).  Since NUL can’t be found, the process fails to launch.
(REG ADD “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Werfault.exe” /v Debugger /t REG_SZ /d NUL /f)

Links

Windows Error Reporting @Microsoft MSDN

Post on Stackoverflow

1. Login as Root user on your ESX server.
2. Type: #esxcfg-hwiscsi –j enable <vmhba#>
3. If successful, you should get the “MTU size successfully set to : 9000” message.
4. To verify the change type: #esxcfg-hwiscsi –l <vmhba#>

All done!

1. Open the GPMC.msc.
2. Create or open a GPO which will be applied to your server(s).
3. Navigate to Computer Configuration\Policies\Administrative Templates\Network\Network Connections.
4. Enable the “Do not show the “local access only” network icon” setting.
5. Close the GPO and GPMC.msc.
6. Run C:\>gpupdate on the server(s) to apply the new policy.

The “No Internet Access” notification should be disabled now.

• You have a computer that has Outlook 2003 (SP2) or 2007, Exchange 2007 Management Tools (32-bit version), PowerShell and .NET Framework installed
• Logon with an account that has Exchange Server Administrator and Local Administrator rights
• You have full access to the users’ mailbox on both servers. See the note below on how to do it.

1. Start the Exchange Management Shell and type the following:[PS] C:\>Get-Mailbox –Database “<Exchange Server FQDN>\<Database Name>” | Export-Mailbox –PSTFolderPath C:\PSTFiles to export all users mailbox to a PST file. Press A for Yes to All. Depending on the size of your database, the export procedure could take a long time to complete.
2. Now the mailboxes are exported to the PST files, make sure that the PST file name matches the alias of the users’ account in the other domain.
3. Next, import the PST files to the other Exchange Server by typing the following: [PS] C:\>Get-Mailbox –Database “<Exchange Server FQDN>\<Database Name>” | Import-Mailbox –PSTFolderPath C:\PSTFiles and press A for Yes for All. Wait until the import operation completes.

Note:
To grant the Administrator Full Access rights on the database type the following command:
[PS] C:\>Get-Mailbox -Database “<Exchange Server FQDN>\<Database Name>” | Add-ADPermission -User Administrator -AccessRights GenericAll

Follow these steps to change the text on a Windows Server 2008 (R2) machine:

1. Logon to your server with the Administrator account.
2. Start RegEdit and navigate to the following key: HKCR\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}
3. If necessary, take the ownership of this key, grant yourself full control rights and then edit the LocalizedString value.
4. In the edit window type: %UserName% on %ComputerName%. Click OK and close RegEdit.
5. Press F5 somewhere on the desktop and the text on the Computer icon should now display the logged on user name.

Tested on Windows Server 2008 R2 Build 7600.

Before you begin, don’t forget to open the default UDP 123 port (in- and outbound) on your firewall.

1. First, locate your PDC Server. Open the command prompt and type: C:\>netdom /query fsmo
2. Log in to your PDC Server and open the command prompt.
3. Stop the W32Time service: C:\>net stop w32time
4. Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist:”0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org”
5. Make your PDC a reliable time source for the clients. Type:C:\>w32tm /config /reliable:yes
6. Start the w32time service: C:\>net start w32time
7. The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
8. Check the Event Viewer for any errors.

Tested on Windows Server 2008 R2 (Build 7600).

Key to press	Action
Windows logo key + Plus Sign or Minus Sign	Zooms in or out
Ctrl+Alt+Spacebar	Preview the desktop in full-screen mode (you have to be zoomed in first)
Ctrl+Alt+F	Switch to full-screen mode
Ctrl+Alt+L	Switch to lens mode
Ctrl+Alt+D	Switch to docked mode
Ctrl+Alt+I	Invert colors (Probably my favorite feature)
Ctrl+Alt+arrow keys	Pan in the direction of the arrow keys
Ctrl+Alt+R	Resize the lens
Windows logo key + Esc	Exit Magnifier