Welcome to TEAMAS. This blog mainly covers Microsoft 365 and Microsoft Power Platform technologies. There are old blog posts on other subjects such as Citrix, Azure, Azure AD, Exchange, Windows, SQL, Android, iOS etc. We hope you enjoy!
There has been talk of Samsung working on an Android build of Jelly Bean for the Samsung Galaxy Ace 2 (I8160) for quite some time. A couple of leaked versions of the build have been available since the end of February and during March, but these contained various bugs as you might expect. On April 2nd, an official release was available on www.sammobile.com and available for install using KIES or OTA, but only for Portuguese customers on the TMN network. This was curious as this network didn't actually sell the phone. It could be a way of getting the early adopters to test this version before the big operators like Telefonica and Vodafone build and release a version themselves. There are many online guides on how to manually download the firmware and apply it to your device, but if you make the direct jump from Gingerbread (2.3) to Jelly Bean (4.1.2) you will likely have RAM issues. The gingerbread versions only allocated around 500MB for RAM whereas J...
This is an overview on the pre-requisites, considerations and changes required in migrate from BES from working with Exchange 2010 over to Exchange 2013 with CU1. The following was tested on a Windows 2003 mixed mode domain and forest functional level where BES Express had already been installed and configured. Update....when I wrote this article originally it was aimed at updating a current Blackberry server to work with Exchange 2013. If you want to migrate your mailboxes over a period of time rather than moving them all at once, you should look to setting a separate BES server which points to the Exchange 2013 server whilst leaving your current BES server pointing to Exchange 2010. In order to migrate the users from one independent database to another to you can the Blackberry Transporter Tool. I found this tool to be excellent as it didn't require any interaction on the BB phones themselves; As far as the end user was concerned, business as usual. ...
Introduction Starting with Windows 10, version 1703, Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro to Windows 10 Enterprise automatically if they are subscribed to Windows 10 Enterprise E3 or E5. The Subscription Activation feature eliminates the need to manually deploy Windows 10 Enterprise or Education images on each target device, then later standing up on-prem key management services such as KMS or MAK based activation, entering GVLKs, and subsequently rebooting client devices. It’s important to note that the Windows 10 Enterprise subscription activation is designed to “step-up” a device from Windows 10 Pro to Windows 10 Enterprise. Therefore, your device is required to have a Windows 10 Pro license activated as a baseline. For Windows 10 Enterprise Subscription Activation to function, there a several prerequisites which need to be in place. This blog is aimed for organisations which have Active Directory on premises an...
Comments
Post a Comment