Windows key: Switch between the Modern Desktop Start screen and the last accessed application.
Windows key + C: To Access the charms bar.
Windows key + Tab: To Access the Modern Desktop Taskbar.
Windows key + I: To Access the Settings charm.
Windows key + H: To Access the Share charm.
Windows key + K: To Access the Devices charm.
Windows key + Q: To Access the Apps Search screen.
Windows key + F: To Access the Files Search screen.
Windows key + W: To Access the Settings Search screen.
Windows key + P: To Access the Second Screen bar.
Windows key + Z: Brings up the App Bar when we have a Modern Desktop App running.
Windows key + X: To Access the Windows Tools Menu.
Windows key + O: Lock screen orientation.
Windows key +. : To Move the screen split to the right.
Windows key + Shift +. : To Move the screen split to the left.
Windows key + V: To View all active Toasts/Notifications.
Windows key + Shift + V: To View all active Toasts/Notifications in reverse order.
Windows key + PrtScn: To Take a screenshot of the screen and automatically save it in the Pictures folder as Screenshot.
Windows key + Enter: To Launch Narrator.
Windows key + E: To Open Computer.
Windows key + R: To Open Run dialog box.
Windows key + U: To Open Ease of Access Center.
Windows key + Ctrl + F: To Open Find Computers dialog box.
Windows key + Pause/Break: To Open the System page.
Windows key + 1 to 10: To Launch a program pinned on the Taskbar in the position indicated by the number.
Windows key + Shift + 1 to 10: To Launch a new instance of a program pinned on the Taskbar in the position indicated by the number.
Windows key + Ctrl + 1 to 10: To Access the last active instance of a program pinned on the Taskbar in the position indicated by the number.
Windows key + Alt + 1 to 10: To Access the Jump List of a program pinned on the Taskbar in the position indicated by the number.
Windows key + B: To Select the first item in the Notification Area and then use the arrow keys to cycle through the items Press Enter to open the selected item.
Windows key + Ctrl + B: To Access the program that is displaying a message in the Notification Area.
Windows key + T: To Cycle through the items on the Taskbar.
Windows key + M: To Minimize all windows.
Windows key + Shift + M: To restore all minimized windows.
Windows key + D: To Show/Hide Desktop (minimize/restore all windows)
Windows key + L: To Lock computer.
Windows key + Up Arrow: To maximize current window.
Windows key + Down Arrow: To Minimize/restore current window
Windows key + Home: To Minimize all but the current window
Windows key + Left Arrow: Tile window on the left side of the screen
Windows key + Right Arrow: Tile window on the right side of the screen
Windows key + Shift + Up Arrow: To Extend current window from the top to the bottom of the screen
Windows key + Shift + Left/Right Arrow: To Move the current window from one monitor to the next
Ctrl + Esc: Switch between Modern Desktop Start screen and the last accessed application
Alt: To Display a hidden Menu Bar.
Alt + D: To Select the Address Bar.
Alt + P: To Display the Preview Pane in Windows Explorer
Alt + Tab: To Cycle forward through open windows
Alt + Shift + Tab: To Cycle backward through open windows
Alt + F: Close the current window Open the Shut Down Windows dialog box from the Desktop
Alt + Spacebar: Access the Shortcut menu for current window
Alt + Esc: Cycle between open programs in the order that they were opened
Alt + F4: Close Application
Alt + Enter: Open the Properties dialog box of the selected item
Alt + PrtScn: Take a screen shot of the active Window and place it in the clipboard
Alt + Up Arrow: To Move up one folder level in Windows Explorer (Like the Up Arrow in XP)
Alt + Left Arrow: To Display the previous folder
Alt + Right Arrow: To Display the next folder
Shift + F6: Cycle backward through elements in a window or dialog box
Shift + F10: Access the context menu for the selected item
Shift + Tab: Cycle backward through elements in a window or dialog box
Shift + Click: Select a consecutive group of items
Shift + Click on a Taskbar button: Launch a new instance of a program
Shift + Right-click on a Taskbar button: Access the context menu for the selected item
Log on to the SP2013-DC1 VM (created in the Part1 of the article).
Server Manager àDashboard à Add Roles and Features.
Select Installation Type (set the default value of Role-based or feature-based installation).
Select Destination Server and Select a Server from the Server pool and click next.
Select Server Roles àActive Directory Domain Services and click Next
Now the Active Directory Domain Services are successfully installed in this Server SP 2013-DC1 and SP2013-DC2. We have already performed the step of initializing the Empty Disks. The next logical step is to perform activity of Promoting the SP2013-DC1 VM as the Domain Controller for the SharePoint 2013 farm that we are going to build.
In this section, we’ll see the necessary steps to configure back-up domain controller. The whole idea is that we’ll not be promoting the back-up DC (SP2013-DC2) as the domain controller for the farm, rather we will be adding the domain controller to the domain (techguru.com) running on primary domain controller VM (SP2013-DC1).
Click ‘Promote this server to Domain Controller’ and select ‘Add a domain controller to an existing domain’. Select credential techgurusp_install and the password for performing this operation.
Now we have successfully installed the domain controller. In the next post, we’ll cover the steps to configure SQL Server 2012 on Microsoft Azure for the SharePoint 2013.
I had a chance to read the book titled ‘SharePoint 2013 Planet of the Apps 2.0’ by Sahil Malik, SharePoint MVP and renowned technology expert. I bought the paperback edition of the book from FlipKart.com few weeks back. The whole idea of buying a book on SharePoint 2013 App model was to have a single reference (one stop shop) for me to ramp up myself on SharePoint 2013 App Model. I’d say that this book has not let me down after purchasing it. Though the book is thin, it’s a well written book by Sahil Malik. The writing style is more of a class-room trainer narration style, which I like very much and keeps reader awake without getting bored. It also helped me to read the book within a day. The technical information presented in this book is very accurate (as per the pre-release SP 2013 timeframe). Personally, I like the following topics in the book, because of the way it is narrated and explained.
The objective of this article is to articulate the setup of SharePoint 2013 farm on Microsoft Azure platform using Infrastructure as a Service (IASS). Basically I pretty much followed the steps mentioned in the MSDN article. I’m using Microsoft Azure trial subscription for the entire setup of SharePoint on Azure.
When it comes to the allocating empty disk space, a size of 20 GB will be allocated to Primary Domain Controller & Back-Up Domain Controller VM. An empty disk size of 50 GB will be allocated to Database Server and SharePoint Server VMs.
Virtual Machine Type
Empty Disk Size
Primary Domain Controller
Backup Domain Controller
When it comes to Subnet creation, it is recommended to create four Subnets for different servers.
Availability Sets in Azure provides the capability to allocate Virtual Machines to different fault domains when a failure occurs. It increases availability and reliability. The recommendation is to create four Availability Sets as per the below conventions
SP2013-DC1 and SP2013-DC2
SP2013-Web1 and SP2013-Web2
SP2012-App1 and SP2013-App2
SP2012-SQL1 and SP2012-SQL2
We’ll be creating an Active Directory Domain by name ‘techguru.com’ (any arbitrary name that you can create for your need. I’ll also be creating the following set of Service Accounts on the techguru.com domain with a password of ‘password-1’ and password set as never expires.
Account to manage the SharePoint farm
Account to Manage the SQL Server (with SysAdmin rights )
Account with Domain administration rights for installing Roles and Features on various servers
The creation of Virtual Machines typically involves the following five steps:-
1) Provisioning of Virtual Machine Instance
2) Creation and Attachment of empty disks
3) Initializing Empty Disks (The specification for empty disks are mentioned in the previous section 1.b)
4) Creation of Availability Set and its Associations for various VMs (The list of Availability Set are mentioned in the previous Section 1.b)
5) Logging into VM and perform initial setup activities
The following set of Virtual Machines need to be created for setting up the SP 2013 Farm. Since I’m having only the Trial version of Azure, I’m selecting only A2 VM with 2 cores of CPU. If you are setting the real Dev-Test SP 2013 environment for your customer on Azure, you need much more than that.
Attach an empty disk of 20 GB to the Domain Controller VM and set it as Read/Write
Now we have attached the empty disk of 20 GB to the primary domain controller (sp2013-dc1) VM. The next step is to create Availability Set for the domain controller VM.
Virtual Machines –> Configure –> Availability Set –> Create an Availability Set
Set the name for availability set as ‘DC Avail Set’ and Save. Now let’s try logging in to VM.
In the Remote Desktop Connection Dialog Box click Connect and provide your user account as <<Machinename>>.cloudapp.netUserName and provide the password. Once we log in to the VM, we need to perform the Task of Initializing the Empty disks (mentioned in previous section)
Attach an empty disk of 20 GB to the back-up Domain Controller VM
Now we have successfully attached the Empty Disk to the backup domain controller VM. The next step is to select the ‘Availability Set’. Select the existing Availability Set of ‘DCAvailSet’ for back-up domain controller and save.
Now we have successfully created Availability Set for Domain Controller VMs (Primary and back-up). Now we need to log in to the SP2013-DC2 VM and perform the Empty Disk Initialization steps mentioned in section 1f.
The empty disk initialization task need to be performed for all the types of the VMs that we would be creating as a part of SharePoint 2013 farm set up. Perform the following task on a VM running Windows Server 2012.
Server Manager à Click File and Storage Services à Disks
Select the Disk that is with the capacity of 20 GB and partition set to Unknown.
Create a new Volume, accept defaults and Set the Drive volume as ‘F’
The next step is to configure the Domain Controllers (both Primary and Back-up), it will be covered in detail in the part 2 of this article.
I was trying to compile the list of frequently asked questions on SharePoint 2013 Remote Event receivers, for my understanding. Here is the list that I compiled.
1. Can we run client-side code from remote event receivers?
No, we cannot run client-side code from remote event receivers
2. How does remote event receiver work fundamentally?
The User performs an action on SharePoint list or library. Based on the action event, the SharePoint communicates with the registered WCF service (defined for remote event). The WCF service communicates with Azure Access Control Services (ACS) and gets signed token from ACS. Using the signed token, the remote WCF services perform necessary action on the SharePoint list or library (based on action).
3. What are the various types of event scopes that are supported?
Remote event receivers are supported at list-level and library-level.
4. How do we debug remote event receivers?
Go to Project Properties in Visual Studio 2012 à SharePoint à Enable remote debugging
Then, set the Azure Service Bus End Point for debugging remote event receivers. Prior to that we need to register for a Windows Azure Service Bus, please check this post http://sundarnarasiman.net/?p=107 for more details on registering an Azure Service Bus.
5. How do we debug remote event receivers?
Go to Project Properties in Visual Studio 2012 à SharePoint à Enable remote debugging
6. Whether the SharePoint 2010 event handler will work automatically after upgrading to SharePoint 2013?
There is no guaranteed that the SP 2010 Event Handler Solution Package will work 100% after upgrade. It may be require re-factoring SP 2010 event handler into an App for SharePoint in SharePoint 2013.
7. Can we have remote event receivers implemented as SharePoint Hosted App in SharePoint 2013?
No. The SharePoint 2013 Remote Event receivers require a WCF service to call back to SharePoint 2013 based on the fired event (remote). In order to host a WCF service, we need a remote Web project, which is feasible only in Auto Hosted App or Provider Hosted App. Hence remote event receivers can’t be implemented as SharePoint Hosted App (as of now).
8. What are the various types of App Models supported by Remote Event Receivers?
a)SharePoint Hosted Apps
b)Provider Hosted Apps
8. Does SharePoint 2013 remote event receivers support synchronous and asynchronous events?
Yes, the remote event receivers have support for both Synchronous and Asynchronous events. It has two methods ProcessEvent and ProcessOneWayEvent :-
ProcessEvent – this typically occurs before an action occurs like when a user adds or deletes and item. It is also called as Synchronous events which typically handles “-ing” events.
ProcessOneWayEvent – this typically occurs after an action occurs. It is also called as Asynchronous events which typically handles “-ed” events.
9. Can we have remote event receivers registered for Host Web in SharePoint?
By default remote event receivers in Visual Studio are registered for App Web only, not Host Web. We can use CSOM to explicitly register the event receiver for Host Web, assuming that App has already requested Permission to manage host web.
10. How SharePoint 2013 Remote event receivers work differently from SharePoint 2010 event receivers?
In SharePoint 2010, the event receivers which handles events of Lists, Libraries or Sites, runs the code on the SharePoint farm itself. In SharePoint 2013, the piece of the code which handles events (WCF) runs outside of SharePoint remotely.
In this article, we’ll see how to create a remote event receiver for a custom list (in App Web) in SharePoint 2013 Online. The Remote Event Receivers are components (classes) that makes SharePoint Apps to respond to events that occur in SharePoint lists or items.
Create a new App in Visual Studio 2012 and name it as ‘CustomListEventReceiver’
Set the Office 365 SharePoint site for debugging the App and select App Type as SharePoint Hosted App
Now the app project is created. The next step is to create or set up a Custom List in the App.
Right Click –> Add New Item –> List and name it as ‘TestCustomList’
Select ‘Default(CustomList)’ for Create a custom list template and list instance of it –> Finish
Now the Custom List is created. The next step is to add the Remote Event Receiver.
Right Click –> Add New Item –> RemoteEventReceiver and name it as TestEventReceiver.
This creates a RemoteWeb Project containing .svc file listening for remote events . The whole ideas is that in SharePoint 2013, the event handling for Lists and Items happened outside of SharePoint in the WCF Service (inside RemoteWeb Project).
Select the following 3 events to be handled
Now you’ll see a remote event receiver project (.svc file inside it) created as the part of the Solution.
Remove the ClientId and ClientSecret from Web.Config file
Open the AppManifest.xml file and change the AppPrincipal to internal
Go to Project Properties in Visual Studio 2012 and set the following properties
Since this App is running in Office 365, we need to set an Azure Service Bus connection string is required for debugging the remote event receiver (.svc component). Otherwise, we’ll get this debugging error mentioned in one of my previous article.
Go to Elements.xml of default.aspx under Pages.xml.