Skip to main content


Showing posts from 2014

AZURE: Creating new VM with static IP address

This case took me whole day. It wasn't easy because of Azure service is still evolving. Commands and dependencies between them are changing, but documentation do not. Some websites and blogs steered me on the course where to find the solution, but I have not found final, working version. Here are the links: So if you are here, you are looking for how to have VM with static IP or you are struggling with problems with creating VM. First thing you must know is that Azure gives your cloud service virtual IP address (VIP). So, even if you are set local network IP for VM's, then still you are using dynamic VIP. If you will stop your virtual machines, then VIP is freed and during next start you will get different IP. To solve this you need to create static VIP. As Microsoft says, you must consider following: Res

How to run Office365 powershell session with one click

If you are managing many companies through the powershell as me, it's easy to switch to other consumer by accident. So you can run your connection and in the last step enter password for different company which ends in redirection to another Office365 tenant, not that one you have needed. Also, it's time waste to enter credentials twice everytime you need to logon to different tenant. I propose you to keep your credentials in files encrypted and prepare separate scripts for every tenant. I assume that you are using Active Directory module for powershell and can successfully connect to Office 365 by powershell.  If not, please find instructions in " Office365: How to connect to from Powershell ". 1.Store PS password in an encrypted form: Read-Host -AsSecureString "Enter password"  | ConvertFrom-SecureString | Out-File c:\temp\PasswordCompany1.txt Copy file with password to the place you want. We will refer to it's path in the next step. 2. Prepare powersh

Office365: Limiting access to Office 365 using ADFS

If you need to restrict access to Office365 for users outside your company at all or just for group of them then you need to use ADFS servers. When you have set them properly and you can be authenticated by ADFS, then you can configure ADFS claims to restrict the Office 365 access. First, I've tried use the solution provided in this link: But, this not work in my environment. I've been looking for article below, but can't find it as "limiting access". Then when asked Microsoft they give me the right link. Thanks! Here is the right link:

Office365: Add new licence / subscription key to the tenant

Hi, Today easy and short tip, but you could wander around for hours searching this: When you have bought new licences you can easily add key to the subscription. Go to the Volume Licencing Center at: (If you have not logged in earlier here you need to register with e-mail account provided with licence order) Get (copy) your subscription key from the license. Next go to this link: and paste the key. That's all! If you have used trial licences you'll have to change your user's licences from trials to the new one.

Perform HP SIM 7.3 installation on Windows Server 2012R2

You will see management installation, not only client one. You can easily get and install client for managing 2012R2 Server from other machine. Problem with SIM installation on 2012R2 Server is because of two things: 1.Setup application have to be run with compatibility settings 2.Server needs to have SQL Server installed Installation of SIM 7.3 step by step. First run of Setup.exe Unsupported OS error Change setup.exe compatibility settings to Windows7 Another try to install There are no active SQL server instances Download SQL Server Express (here 2012 version) Choose components: here SQL x64 and Management Studio_x64 Perform a new installation of SQL Server 2012 Choose instance name: here HPSIM Choose service accounts and services startup type Choose authentication mode and administrator account(you have to add one) It goes Instance is yet stopped and disabled Change startup type to automatic and start service Installation of management tools Installation succeded Run SQL Management

Office 2013 and Exact Globe Next prior to 406 - cannot run Excel reports

When you have to upgrade your Office installation to 2013 version and using Exact Globe Next version before 406 then you cannot run Excel reports by default. Office 2013 is not officially supported with Exact Globe Next version prior to 406. But wait, there is a workaround to make both working, i.e. to run Excel 2013 reports on Exact Globe version 401 for example. First you should try to install Office2010 on the top of the Office2013 and reinstall Exact Globe Next. Just install Office 2010 as a second Office version and reinstall Exact Globe. Then you can uninstall Office2010. For me it worked for the two of three computers. If you still cannot run Excel reports, then go to check your Windows registry: 1.Run regedit 2.Go to HKEY_CLASSES_ROOT 3.Check if Excel.Application key is present. 4.If not, create it, and create subkey CLSID 5.Probably as option, but create the second subkey - CurVer 6.Go to HKEY_CLASSES_ROOT\Excel.Application.15\CLSID 7.Copy data value from (Default) 8.Go to Go

Outlook2013: Outlook hangs when loading profile

If your Outlook is trying to load the profile, but it lasts forever, check the following: Run Outlook with Ctrl key pressed. This will run Outlook in safe mode. If Outlook works, then do the following: 1. Run  regedit   2. Browse to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common 3. Create a new key named " Graphics " 4. In graphics key, create a New DWORD (32-bit) Value  named  DisableHardwareAcceleration . 5. Enter Value data as 1

Office365: Cannot move, migrate mailbox. The operation couldn't be performed because object couldn't be found on...

The operation couldn't be performed because object couldn't be found on... This error appears when you try to move (migrate) mailbox from on premises Exchange to the Office365. It means that object with same date exists in both sides and it differs in some way. It could happen if you have created mailbox in Office365 without migration from on premises Exchange. To resolve this issue, you need to remove user from Office365 side and synchronize it again and then migrate mailbox to the cloud. So, connect to Office365 from Powershell. Then run: Remove-MsolUser -UserPrincipalName Next, run: Remove-MsolUser -UserPrincipalName m -RemoveFromRecycleBin Now, wait for dirsync replication or force it and you should have the ability to move the mailbox to Office365 from onprem Exchange.

Office365: MRSProxy.svc issue - update

Some time ago I wrote a post about MRSProxy.svc problems: I have not got into account migration endpoint settings. When this issue appeared again and I cannot move mailboxes to the Office365 at all, then I have checked endpoint settings. It seemed that the password used for migration endpoint has been changed by other administrator and was not refreshed in Office 365 panel. After entering password again, I can again move mailboxes! To change migration endpoint password, go to: Exchange administrative panel, users, migration. On the right, low corner, check migration endpoint , click Details Change password for administrator or enter new admin credentials.

Office365: Cannot remove custom domain

When you need to remove one of your custom domains from Office 365 you can find that you cannot do this. One of possible issues with this is when you are working in hybrid environment and if you have DirSync working which synchronizes your AD to the Microsoft cloud. This is one of undocumented behaviors of Office 365, that you cannot remove domains, i.e. not all of them, cause I have just done this without problems with some, but still cannot do this with others. When I have searched for resolution on Office365 Community and other Google sites and blogs, I found nothing than " Before you remove a domain name from Office 365, you have to remove anything that is using the domain name ": Fortunately, if you are working in hybrid environment, the shorter path exists. First login to your Office 365 tenancy from powershell: Connect-MSolService Run: Get-MsolUser -DomainName If

Windows Store doesn't work after upgrade to Windows 8.1

After moving from Windows 8 to 8.1 you may see that Windows Store no longer works. To fix this, use this path: 1. Run CMD or powershell as an administrator 2. Enter this in cmd: powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml 3. Type: start "" "ms-windows-store:"

Exchange 2010: EMC initialization failed

When you remove one of your Exchange servers, then you have chance to encounter EMC initialization error. This is because removed server was chosen as the best to be managed by EMC. you can delete this mapping and enforce EMC to choose another server. To erase MMC settings, do the following: 1. Go to the  c:\Users\ username \AppData\Roaming\Microsoft\MMC 2. Delete “Exchange Management Console” file: 3. Run regedit 4. Delete this key: 

Configuring SMTP relay for Office365 / Exchange Online

You've just migrated your mailboxes to the Office365. But what to do with copiers & printers which don't want to work with Office365 account, because they don't allow to use TLS? Or how to send error or information events from your servers if you are using simple SMTP send? Answer is - install SMTP server feature! I will show you how to do this using 2012R2 server as a relay for SMTP. First: you need to install SMTP on the server 1. Go to server manager, click Add roles and features and select SMTP Server feature. Standard installation is simple -after clicking 'Next' several times and 'Finish' in the wizard you will have SMTP server installed on your machine. 2. Go to the Server Manager again and click Tools: Internet Information Services (IIS) 6.0 Manager . SECOND: configure SMTP server properties 3. Click on the [SMTP Virtual Server #1] and right click for properties 4. In the General tab in IP address section, select Advanced... : Here you can conf