This deletes all the user related information in outlook. All email accounts and local storage deleted.

After this, I ran “defaults delete com.microsoft.Outlook” once more and restarted Outlook 15.8 – this time it worked, but beware, you start from scratch losing all account info and locally stored emails. for runiing this

Open the Terminal app (usually found in Launchpad ▸ Other) and on the command line type: “defaults delete com.microsoft.Outlook” (without quotation marks) followed by Enter.

But after re-downloading all emails from the server, Outlook works again.

Access hidden user library files | Mac OS 10.7 and later

Method 1

In the Finder, choose Go > Go To Folder.

In the Go To Folder dialog, type ~/Library

Click Go.

Method 2

Hold down the Alt (Option) key when using the Go menu. The user library folder is listed below the current user’s home directory.

Note: After you open the Library folder, you can drag the Library icon from the top of that window to the Dock, Side Bar, or toolbar. That way, it’s readily accessible.

To help address these challenges, today we are also releasing a preview of Azure Active Directory Connect Health in the Azure Preview Portal. This feature of Azure Active Directory Premium helps you monitor and gain insight into health, performance and login activity of your on-premises Active Directory infrastructure. While this release supports Active Directory Federation Services (ADFS), we are already working to add support for sync servers in the future.

This release for ADFS has three key capabilities:

Alerts based on events, configuration information, synthetic transactions and perf data. So, when something goes wrong, or is about to go wrong, we let you know.

Graphs of login activity that you can pivot multiple ways for easy viewing. These “usage insights,” are accessible when you enable auditing on your ADFS servers. They are based on audits generated when user’s login and tokens are generated for applications.

Getting this functionality requires downloading and installing an agent on each of your ADFS servers. The Azure AD Connect Health service processes data the agents send to the cloud, displaying alerts and other views into the ADFS service. We support ADFS 2.0 on Windows Server 2008, 2008R2 as well as ADFS in Windows Server 2012 and 2012R2. The agents are supported on ADFS proxy as well as Web Application Proxy servers.

Installing the agent

The first step is to install the agent on each of your ADFS and ADFS proxy/Web Application proxy servers.

Login into the Azure Preview Portal with your Azure AD global administrator account. This account must also be licensed for Azure AD premium.

Click on the Marketplace tile. Under Identity you will find the Azure AD Connect health extension.

Click on it to enable the service and gain access to Azure AD Connect Health within the portal.

Click on the Quick Start tile and download the agent onto your ADFS and proxy servers.

Install the agent that you just downloaded.

Fire up a PowerShell window. Use the Register-ADHealthAgent commandlet to configure and register the health agent to securely connect to the Azure AD Connect Health service. You will need admin credentials.

Using the Portal to view the health and usage of ADFS

The portal is comprised of three key views. Let’s dive into some of the details.

Alerts

The Azure AD Connect Health Alerts section shows you the list of active alerts requiring administrator attention, which are based on ADFS service events, performance counters and configuration information. These could be issues with certificates, connectivity to domain controllers or as simple as detecting that the ADFS service is not running. They can also warn of potential issues.

Selecting an alert reveals more detailed information, as well as resolution steps and links to relevant documentation. You can also view historical data on previously resolved alerts.

Usage Analytics

Usage analytics provide insight to login activity based on security audits that each of the ADFS servers generates and sends to the Azure AD Connect Health for analysis.

Currently we support two views:

Successful logins can be viewed by application (relying party trust), network location, authentication method or server. The application pivot is tremendously useful for understanding usage patterns of applications.

Unique user count shows the number of unique users accessing applications and can be viewed by application (relying party trust).

To select additional metrics, specify a time range, or change the grouping, simply right-click on the usage analytics blade and select Edit Chart.

We will add views in the near future that show the count and type of issuance failures, such as username/password failures, occurring in the system. If you need addition views, we welcome your feedback.

Performance Data

This is a simple, aggregated view of key performance counters collected from your ADFS and proxy servers, including token requests, CPU, memory and latency. It can also help you detect potential balancing issues within your environment.

Using the Filter option at the top of the blade, you view an individual server’s metrics. To change metrics, simply right-click on the monitoring chart under the monitoring blade and select Edit Chart. You can then select additional metrics and specify a time range for viewing the performance data.

Data Loss Protection (DLP)—Over the last few years we’ve added DLP to Exchange, Outlook, OneDrive for Business and SharePoint. Now we’re bringing these same classification and policy features to Word, Excel and PowerPoint. With these new capabilities, IT admins can centrally create, manage and enforce polices for content authoring and document sharing—and end users will see policy tips or sharing restrictions when the apps detect a potential policy violation.

Outlook—We’re delivering a number of significant technical improvements to Outlook.

MAPI-HTTP protocol. We’ve replaced the RPC-based sync with a new Internet-friendly MAPI-HTTP protocol that supports Exchange/Outlook connectivity.
Foreground network calls. We’ve eliminated the use of foreground network calls to ensure that Outlook stays responsive on unreliable networks.
Multi-factor authentication. With this release of the Outlook client, we’ll support multi-factor authentication through integration with the Active Directory Authentication Library (ADAL).
Email delivery performance. We’ve reduced the amount of time it takes to download messages, display the message list, and show new email after resuming from hibernation.
Lean storage footprint. We’ve added settings that allow users to better manage storage by only retaining 1, 3, 7, 14 or 30 days of mail on the device.
Search. We’ve improved the reliability, performance, and usability of Outlook search, and integrated the FAST-based search engine in Exchange.
Click-to-Run deployment—For customers on our Office 365 subscription service, the 2016 release includes new deployment features that IT pros have been asking for:

Better network traffic management. We’re introducing a new Background Intelligence Transfer Service (BITS) to help prevent congestion on the network. BITS throttles back the use of bandwidth when other critical network traffic is present.
Enhanced distribution management. We’re improving our integration with System Center Configuration Manager (SCCM) to allow IT admins to efficiently download and distribute monthly Office updates using the native SCCM features.
Flexible update management. We’ve created a way for admins to manage the pace at which they receive feature updates and bug fixes while continuing to receive regular security updates.
Simplified activation management. We’re adding a feature in the Office 365 Admin Portal to allow admins to manage device activations across users.
Macros and Add-ins—We’re not making any changes to Macros or Add-ins in this release. It’s rare that “no changes” is a something we’d want to highlight, but we think it’s worth celebrating the consistency in the programming model across releases. We understand how important this is and we’re committed to a high level of compatibility as we continue to innovate. (See dev.office.com for more on how we’re innovating in Office extensibility.)

Accessibility—We’ve improved keyboard accessibility for high-value Excel features like PivotTables and Slicers, addressed a number of readability issues in Outlook, and introduced a dark theme for users with visual impairments.

These are just some of the new capabilities IT pros and developers will experience in the Preview. We’re excited about this milestone in our development process and are looking forward to hearing your feedback. For more details on the Office 2016 Preview program and instructions on how to download the applications, please visit the Office 2016 Preview program on the Microsoft Connect site. We’ll continue to update the product with new features as they become available and will periodically highlight significant announcements here along the way.

Like this:

Migration Assistant transfers your accounts, documents, and settings from another computer to your Mac.Migration Assistant and Setup AssistantSetup Assistant opens the first time you start up a new Mac. It helps you enter your information about your network, and guides you through setting up a user account on your computer. Use it to transfer user accounts, settings, and documents from another computer to your Mac. If you don’t use Setup Assistant to transfer information when you first set up your new Mac, you can do it later using Migration Assistant.Migration Assistant in Mavericks and Yosemite can transfer information from other computers that have OS X Snow Leopard v10.6.8 or later installed. If you’re migrating from a computer with an earlier version of OS X, update your older computer first, or manually copy your data from one computer to another.If you’re migrating from a Windows-based PC to a Mac, you can use the Windows Migration Assistant as part of this process.Before you beginIf you’re using a Mac notebook, make sure its power adapter is connected and plugged in.Use Software Update on both the source and destination computers to confirm that the latest updates are installed.On the source (original) Mac, make sure that you have updated your third-party software before migrating.On the source Mac, open System Preferences, click Sharing, then make sure you’ve entered a name in the Computer Name field.About FileVaultAs part of setup or migration, you might be asked if you want to use FileVault. FileVault encrypts your startup drive. This helps to prevent others from viewing information stored on your computer without the right user name and password. If you change your mind after setup or migration, you can enable or disable FileVault from the Security & Privacy pane of System Preferences at any time.When two user accounts have the same nameIf your new Mac already has a user account with the same name as one you’re trying to transfer, Migration Assistant lets you decide what to do. You can either replace the existing user on your new Mac, or give the user you’re migrating a new account name.Selecting the option to replace an existing user overwrites that user’s Home folder on your new Mac. This can be convenient if you just set up your new Mac using the same account name and of your important data is still on your original Mac. Don’t select the option to replace the existing user unless you’re certain you don’t have any important files stored in this user’s Home folder on your new Mac.If you aren’t keeping your original computerIf you’re migrating user accounts, music, documents, and other files from a computer you no longer plan to use, you might want to do these things:If the computer you’re no longer using has content purchased from the iTunes Store, you should deauthorize it.If the Mac you’re no longer using is signed into iCloud, turn off “Find My Mac” if it’s on, and sign out of iCloud from the iCloud pane of System Preferences before selling or giving it away.Choose a connection methodThere are several ways to transfer information from one computer to another with Migration Assistant. Choose the one you want to use. Wi-Fi orEthernet Thunderboltor FireWire Time Machineor external drive From a WindowscomputerMigrate using a Wi-Fi or Ethernet network connectionMake sure both of the Macs you’re using are connected to the same network, either wirelessly or using an Ethernet cable.

If your network connection is slow, you can connect a single Ethernet cable between your two computers at any time during migration to transfer information. Migration Assistant detects the new connection, and automatically switches to Ethernet without having to start your migration over again.

On your new Mac, open Migration Assistant. You can find it by choosing Go > Utilities, or using Spotlight or Launchpad.Once the Migration Assistant window opens, click Continue.Enter an admin password when prompted, and click OK.On your older Mac, open Migration Assistant.Once the Migration Assistant window opens, select the option to migrate your data “To another Mac”, and click Continue. Enter an admin password when prompted.Select the system that you want to migrate from, then click continue. The continue button will be unavailable (dimmed) until you select a source.

If you see a security code appear, confirm the same security code is displayed on both of your computers. Then, click Continue on the source computer.You can customize the type of information that is migrated on the next screen. If you want to transfer only a portion of an account, deselect anything you don’t want migrated. If there is more than one user on your original Mac, you can click the triangle next to a user’s icon and deselect anything you don’t want to migrate for specific users.

After you click Continue, the Migration Assistant begins transferring files to your new Mac. The amount of time that it takes for migration to complete depends on the amount of data being copied, and the speed of the connection.

When migration finishes, the login window reappears. Log into the migrated account on your new Mac to see your files.Migrate using a Thunderbolt or FireWire cableYou can transfer your data between two Macs using a Thunderbolt cable or FireWire cable.Connect your two Macs using either a Thunderbolt or FireWire cable.If the original Mac is started from OS X Mountain Lion or earlier, or if you’re using a FireWire cable to migrate, restart the original computer and hold down the T key at startup to start it in Target Disk Mode.On your new Mac, open Migration Assistant. You can find it by choosing Go > Utilities, or using Spotlight or Launchpad.When your new Mac asks you for a migration method, select “From a Mac, Time Machine backup, or startup disk”, and click Continue.

Select the system that you want to migrate from, then click continue. The continue button is unavailable (dimmed) until you select a source.

Confirm the same security code is displayed on both machines before clicking Continue on the source computer.You can customize the type of information that is migrated on the next screen. If you want to transfer only a portion of an account, deselect anything you don’t want migrated. If there is more than one user on your original Mac, you can click the triangle next to a user’s icon and deselect anything you don’t want to migrate for specific users.

After you click Continue, the Migration Assistant transfers your files to your new Mac. The amount of time that it takes for migration to complete depends on the amount of data being copied.Once migration finishes, the login window reappears. Log into the migrated account on your new Mac to see your old files. Migrate from a Time Machine backup or external driveUse these steps to migrate users, data, or other information from an existing Time Machine backup stored on a Time Capsule or external drive.If your Time Machine backup is on an external drive, connect the drive to your new Mac.On your new Mac, open Migration Assistant. You can find it by choosing Go > Utilities, or using Spotlight or Launchpad.Enter an admin password when prompted, and click OK.Select “From a Mac, Time Machine backup, or startup disk”, then click Continue.

Select the Drive, Time Machine backup, or Time Capsule volume you want to migrate from, then click Continue. The Continue button is unavailable (dimmed) until you select a source.

If you’re migrating from a Time Capsule, enter your Time Capsule password when prompted, then click Connect.Select the specific Time Machine backup you want to migrate from, then click Continue.

You can customize the type of information that is migrated on the next screen. If you want to transfer only a portion of an account, deselect anything you don’t want migrated. If there is more than one user on your original Mac, you can click the triangle next to a user’s icon and deselect anything you don’t want to migrate for specific users.

After you click Continue, the Migration Assistant begins transferring files to Mac. The amount of time that it takes for migration to complete depends on the amount of data being copied, and the speed of the connection.Once migration finishes, the login window reappears. Log into the migrated account on your new Mac to see your old files.Migrate from a Windows computerYou can also migrate data from a Windows computer to your Mac if your PC uses Windows XP SP2 or later.Download and install Windows Migration Assistant on your PC.Make sure your Macs are connected to the same network, either wirelessly, or using an Ethernet cable.On your PC, open Migration Assistant.On your Mac, open Migration Assistant. You can find it by choosing Go > Utilities, or using Spotlight or Launchpad.Follow the onscreen prompts to finish migration. See About Windows Migration Assistant for more information, including which files can be transferred and where you can find them on your Mac.

This article provides instructions on setting the hostname of a Mac OS X workstation from the terminal.

This can be useful when configuring your workstation remotely through ssh, or when you need to change the fully qualified hostname of the workstation (which can’t be done from the UI).

Note: The following procedure is for informational purposes only and is not an Autodesk certified or supported workflow. Should issues arise with this procedure, they will not be addressed by Autodesk Customer Support.

ProcedurePerform the following tasks to change the workstation hostname using the scutil command.Open a terminal.Type the following command to change the primary hostname of your Mac:This is your fully qualified hostname, for example myMac.domain.comsudo scutil –set HostName “<new host name>”Type the following command to change the Bonjour hostname of your Mac:This is the name usable on the local network, for example myMac.local.sudo scutil –set LocalHostName “<new host name>”Optional: If you also want to change the computer name, type the following command:This is the user-friendly computer name you see in Finder, for example myMac.sudo scutil –set ComputerName “<new name>”Flush the DNS cache by typing:dscacheutil -flushcacheRestart your Mac.

Azure RemoteApp uses a Windows Server 2012 R2 template image to host all the programs that you want to share with your users. To create a custom RemoteApp template image, you can start with an existing image or create a new one. The requirements for the image that can be uploaded for use with Azure RemoteApp are:

The image size should be a multiple of MBs. If you try to upload an image that is not an exact multiple, the upload will fail.

The image size must be 127 GB or smaller.

It must be on a VHD file (VHDX files are not currently supported).

The VHD must not be a generation 2 virtual machine.

The VHD can be either fixed-size or dynamically expanding. A dynamically expanding VHD is recommended because it takes less time to upload to Azure than a fixed-size VHD file.

The disk must be initialized using the Master Boot Record (MBR) partitioning style. The GUID partition table (GPT) partition style is not supported.

The VHD must contain a single installation of Windows Server 2012 R2. It can contain multiple volumes, but only one that contains an installation of Windows.

The Remote Desktop Session Host (RDSH) role and the Desktop Experience feature must be installed.

The Remote Desktop Connection Broker role must not be installed.

The Encrypting File System (EFS) must be disabled.

The image must be SYSPREPed using the parameters /oobe /generalize /shutdown (DO NOT use the /mode:vm parameter).

Create a user account in Active Directory to use as the RemoteApp service account. Restrict the permissions for this account so that it can only join machines to the domain. See Configure Azure Active Directory for RemoteApp for more information.

Create a dynamically expanding VHD of 40 GB or more in size. (Estimate the amount of space needed for Windows, your applications, and customizations. Windows Server with the RDSH role and Desktop Experience feature installed will require about 10 GB of space).

This will run for several seconds. When the VHD creation is complete, you should see a new disk without any drive letter and in “Not initialized” state in the Disk Management console.

Right-click the disk (not the unallocated space), and then click Initialize Disk. Select MBR (Master Boot Record) as the partition style, and then click OK.

Create a new volume: right-click the unallocated space, and then click New Simple Volume. You can accept the defaults in the wizard, but make sure you assign a drive letter to avoid potential problems when you upload the template image.

Right-click the disk, and then click Detach VHD.

Install Windows Server 2012 R2:

Create a new virtual machine. Use the New Virtual Machine Wizard in Hyper-V Manager or Client Hyper-V.

On the Specify Generation page, choose Generation 1.

On the Connect Virtual Hard Disk page, select Use an existing virtual hard disk, and browse to the VHD you created in the previous step.

On the Installation Options page, select Install an operating system from a boot CD/DVD_ROM, and then select the location of your Windows Server 2012 R2 installation media.

Choose other options in the wizard necessary to install Windows and your applications. Finish the wizard.

After the wizard finishes, edit the settings of the virtual machine and make any other changes necessary to install Windows and your programs, such as the number of virtual processors, and then click OK.

Connect to the virtual machine and install Windows Server 2012 R2.

Install the Remote Desktop Session Host (RDSH) role and the Desktop Experience feature:

Launch Server Manager.

Click Add Roles and features on the Welcome screen or from the Manage menu.

On the Confirm installation selections page, select Restart the destination server automatically if required, and then click Yes on the restart warning.

Click Install. The computer will restart.

Install additional features required by your applications, such as the .NET Framework 3.5. To install the features, run the Add Roles and Features Wizard.

Install and configure the programs and applications you want to publish through RemoteApp.

Important:

Microsoft recommends that you install the RDSH role before installing applications to ensure that any issues with application compatibility are discovered before the image is uploaded to RemoteApp.

Make sure your application appears in the Start menu. Also ensure that the icon you see in the Start menu is what you want users to see. If not, change it. (You do not have to add the application to the Start menu, but it makes it much easier to publish the application in RemoteApp. Otherwise, you have to provide the installation path for the application when you publish the app.)

Disable the Encrypting File System (EFS). Run the following command at an elevated command window:

Fsutil behavior set disableencryption 1

Alternatively, you can set or add the following DWORD value in the registry:

HKLMSystemCurrentControlSetControlFileSystemNtfsDisableEncryption =1

If you are building your image inside an Azure virtual machine, rename the %windir%PantherUnattend.xml file, as this will block the upload script used later from working. Change the name of this file to Unattend.old so that you will still have the file in case you need to revert your deployment.

Go to Windows Update and install all important updates. You might need to run Windows Update multiple times to get all updates. (Sometimes you install an update, and that update itself requires an update.)

SYSPREP the image. At an elevated command prompt, run the following command:

C:WindowsSystem32sysprepsysprep.exe /generalize /oobe /shutdown

Note: Do not use the /mode:vm switch of the SYSPREP command even though this is a virtual machine.

Next steps

Now that you have your custom template image, you need to upload that image to your RemoteApp collection. Use the information in the following articles to create your collection:

Uploading and Downloading VHDs to Windows Azure

One of the great features of Windows Azure is VHD mobility. Simply put it means you can upload and download VHDs to and from the cloud.

Technical Notes

A few things to point out while I’m here. Currently, Windows Azure only supports the VHD file format in a fixed disk format. That being said the Add-AzureVHD cmdlet supports converting a dynamic VHD on upload to a fixed VHD so you do not have to worry about converting them up front.

Also, both the Add-AzureVHD and Save-AzureVHD cmdlets have intrinsic knowledge of the VHD file format and during upload or download only copy the written bytes and skip the empty. This is a huge optimization!

When the code above is run the uploaded VHD will be registered in Windows Azure as a data disk named ‘mydatadisk’. Refresh the portal and you will see it in the Disks list and it will also be available for attaching to a virtual machine.

If you are uploading a VHD with an operating system on it you need to tell that to Windows Azure.

Register VHD as an OS Disk

This code registers the disk as bootable. Meaning you can now create a virtual machine and specify this disk as the boot disk.

As I mentioned above you can specify a disk to boot from instead of provisioning from an image. The PowerShell code to do so is simple. You can of course add disks and endpoints in between New-AzureVMConfig and New-AzureVM as well.

Install Windows Azure PowerShell

When prompted, click Run. The Microsoft Web Platform Installer loads, with the Windows Azure PowerShell module available for installation. The Web Platform Installer installs all dependencies for the Windows Azure PowerShell cmdlets

Connect to your subscription

The PowerShell cmdlets require your subscription information so that it can be used to manage your services. As of the .0.7 release of the module, In order to do that I downloaded the management certificate that contains the information needed to connect PowerShell to my Azure subscription.

The Windows Azure PowerShell module includes cmdlets that help you download and import the certificate. I started PowerShell from the start Screen

The Get-AzurePublishSettingsFile cmdlet opens a web page on the Windows Azure Management Portal, from which you can download the subscription information. The information is contained in a .publishsettings file.

Once saved, I used the Import-AzurePublishSettingsFile to imports the .publishsettings file for use by the module. This file includes a management certificate that has security credentials.

View account and subscription details

You can have multiple accounts and subscriptions available for use by Windows Azure PowerShell. You can add multiple accounts by running Add-AzureAccount more than once. To see the available accounts, type:

Over the last 10 years, businesses, scientists and hobbyists from all over the world have been using Google Earth Pro for everything from planning hikes to placing solar panels on rooftops. Google Earth Pro has all the easy-to-use features and detailed imagery of Google Earth, along with advanced tools that help you measure 3D buildings, print high-resolution images for presentations or reports, and record HD movies of your virtual flights around the world.

Starting today, even more people will be able to access Google Earth Pro: we’re making it available for free. To see what Earth Pro can do for you—or to just have fun flying around the world—grab a free key and download Earth Pro today. If you’re an existing user, your key will continue to work with no changes required.

Is there a way to set up a rule so that all emails from a specific server (example microsoft.com) go into a specific folder? I can do it individually each time someone from work emails me but want to set it up so that people from microsoft.com who have never emailed me would automatically go into my MS folder?

Microsoft Outlook 2010 and 2013 users: Outlook’s Rules Wizard includes a condition for “specific words in the sender address” which you can use instead of this rule. (But this rule still works.)

Step 1: Begin creating the rule, choosing the “From people or public group” or “specific words in the sender address” condition. Instead of selecting a contact from the Address list, type the domain portion of the address in the Address field.