01 ott 2017

Hyper-V 2012 R2 - 2016: Automatic Virtual Machine Activation

#Note
Automatic Virtual Machine Activation ( AVMA ) is a feature that was introduced in Windows Server 2012 R2. AVMA simply binds the VM activation to the licensed virtualization server and activates the VM when it starts up. This way it is eliminates the need to enter licensing information and activate each VM individually.

AVMA requires that the host is running Windows Server 2012 R2 Datacenter or later and that the guest virtual machine OS is Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, or a later version.

#Product affected / related
Windows Server 2012 R2 and later with Hyper-V role

#Solution
Once the Hyper-V host is activated and the guest VMs are running (without activation of course), the only  step required is to install the AVMA client key on the guest VMs (Data Center or Standard). To manually install the key using the command line, please use the following syntax from an elevated Command Prompt inside the guest OS:

C:\>slmgr.vbs /ipk <AVMA Key>

The following AVMA are public keys that can be used for Windows Server 2012 R2:

Edition                                 AVMA key 
Datacenter                         Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW
Standard                             DBGBW-NPF86-BJVTX-K3WKJ-MTB6
Essential                              K2XGM-NMBT3-2R6Q8-WF2FK-P36R2

The following AVMA are keys that can be used for Windows Server 2016:

Datacenter                         TMJ3Y-NTRTM-FJYXT-T22BY-CWG3J
Standard                             C3RCX-M6NRP-6CXC9-TW2F2-4RHYD
Essential                             B4YNW-62DX9-W8V6M-82649-MHBKQ

30 ago 2017

Windows Server Evaluation: Convert and activate to fully licensed editions

#Note
Windows Server Evaluation: Convert and activate to fully licensed editions

#Product affected / related
Windows Server 2012 or higher

#Issue 
End user not able to use corporate or OEM serial numbers on Eval. Edition

#Solution
1. You need to establish your exact currently installed version. From a elevated command prompt, run the following command:

DISM /online /Get-CurrentEdition


2. Running the following command with your license key. Delete "Eval"from edition.

DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

24 ago 2017

Test EOP anti-spam with GTUBE ("Generic Test for Unsolicited Bulk Email")

#Note 
Test EOP anti-spam

#Product affected / related
Exchange Online Protection, Antispam filter in general

#What's GTUBE
The GTUBE ("Generic Test for Unsolicited Bulk Email") is a 68-byte test string used to test anti-spam systems, in particular those based on SpamAssassin. In SpamAssassin, it carries an antispam score of 1000 by default, which would be sufficient to trigger any installation.

The contents of the string are as follows:


 XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X  

and should be placed in the message body of an RFC 5322 compliant email message, without any linebreaks or whitespaces.


There exist some varieties, notably the NAItube (which will carry a variable weight) and the GTphish (which will trigger specifically as a phishing mail), which are used in the McAfee implementation of SpamAssassin.


#Solution
To test Exchange Online Protection to detects spam messages, you can send a so-called GTUBE message to one of your recipients. The GTUBE message works in similar way that the  EICAR antivirus test file does. However, instead of adding a malicious attachment, the message body contains a specific string "XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.3 4X" which should always trigger the anti-spam engine to mark the message as spam. To test the anti-spam engine, send a message to a recipient in your domain and include the string below in the body of the message. Note that there should not be anything else in the body and that the string must be on a single line, without any spaces, or other.   You don't need to create a rule to catch this message. Exchange Online Protection will automatically detect it as spam

05 ago 2017

Storing messages sent by delegates [Send On Behalf, Send As]

By default, Exchange Online keeps a copy of all messages sent by delegates from a shared mailbox in the Sent Items folder of the user who sends the message. This is insane because it is usually more efficient to have the messages stored in the shared mailbox.

This Cmdlet manage the right properties

 Set-Mailbox –Identity 'sharedmbx' –MessageCopyForSendAsEnabled $True –MessageCopyForSendOnBehalfEnabled $True  

The MessageCopyForSendAsEnabled property is False by default. If set to True , Exchange Online keeps messages sent by delegates as the shared mailbox in the delegate's mailbox and also creates a copy in the shared mailbox. The same about MessageCopyForSendOnBehalfEnabled property.



31 lug 2017

MAPI over HTTP will be the sole connection protocol used by Exchange Online after October 31, 2017

#note

MAPI over HTTP will be the sole connection protocol used by Exchange Online after October 31, 2017. All Outlook clients have to be updated to a version that supports MAPI over HTTP by that date.