I received my Surface Pro 3 last week and have spent the week-end setting it up. After disabling Hyper-V (I need VirtualBox) I wanted to create a “Battery Saving” profile as I did previously on my Surface Pro 2 following these instructions but could not find any settings except the basic ones.
Operational reporting and dashboarding using Microsoft Business Intelligence Solutions: A great looking, relevant, informative dashboard for the executive is the ultimate end goal for most Business Intelligence projects. Microsoft has all of the tools necessary to get data from your transactional systems into an effective dashboard.
– Tags: bi
Windows Azure Pack from A to Z, a video series: It’s no secret that the Microsoft Cloud OS Vision and “private cloud” are pretty hot topics these days.
– Tags: azure
Hortonworks Sandbox: Sandbox is a personal, portable Hadoop environment that comes with a dozen interactive Hadoop tutorials. Sandbox includes many of the most exciting developments from the latest HDP distribution, packaged up in a virtual environment that you can get up and running in 15 minutes!
– Tags: bi
Microsoft BI Authentication and Identity Delegation: Microsoft BI Authentication and Identity Delegation Technical Reference Guide
- Support of the L developer preview
- Fixed issued with google launcher (no stats)
- New circular gauges (bar can still be selected from settings)
- Some minor UI tweaks
- Update to Dashclock 2.0 API
- No need to enable root features in settings anymore
- Various performance and memory optimizations
- Fixes from crash reports
- …. and much more
This article is a short description on setting up a point-to-site VPN from a developer PC to a network defined in an Azure subscription. The long form of this setup can be found here.
The setup follows these steps:
- Set up an Azure virtual network with a gateway
- Create the root and client certificates
- Connect a client to that gateway
Set up an Azure virtual network
An Azure virtual network consists in three distinct configurations:
- The point-to-site connectivity address space: the address space client will be added to when connecting to the gateway
- The virtual network address space: the address space for virtual machines running in the virtual network
- The virtual network DNS configuration
- A root certificate
- From the Azure portal go to networks and select “New”
- Select “Custom create”, name the network and let Azure create an affinity group
- Enter 220.127.116.11 (google) and 18.104.22.168 (google2) as DNS servers and select “Configure a point-to-site VPN”
- Define the point-to-site connectivity address space: 172.16.0.0/24
- Define the virtual network address space (10.0.0.0/8), including a subnet (10.0.0.0/11)and a gateway subnet (10.32.0.0/29)
- Create the gateway (action at the bottom of the screen)
You can also grab this configuration and just import it.
Create the root and client certificates
We will use
makecert to create certificates. Makecert ist installed as part of Visual Studio 2013.
makecert -sky exchange -r -n "CN=PRMgmtRootCert" -pe -a sha1 -len 2048 -ss My "PRMgmtRootCert.cer" creates the certificate (.cer file), saves it to the local keystore and to the named file. You then need to upload the file it into the certificates section of the Azure virtual network.
makecert.exe -n "CN=PRMgmtClientCert1" -pe -sky exchange -m 96 -ss My -in "PRMgmtRootCert" -is my -a sha1 creates a client certificate to the local keystore.
In order to export the client certificates use the keystore manager (
certmgr.msc), select all tasks and export the client certificate with the private key. This will be a .pfx file. Make sure to record or remember the password (key) that you set for this certificate.
Connect a client to the gateway
- Go to the dashboard of the virtual network in the Azure potal and download the client (32 or 64-bit version depending on your needs)
- On the client that will establish the point-to-site VPN import the client certificate (.pfx file), confirm the password and establish the VPN
Now that we have established a point to site VPN we can:
- add virtual machines to the virtual network (in the 2nd step make sure that “Create Could Service” is selected in order to be able to select the virtual network)
- delete the public endpoints of those machines in case they shall only be reache through the VPN
- connect to the virtual machines (RPD, powershell) using the private IP addresses (in the VPN’s address space)
Fortunately the Client Side Object Model (CSOM) comes to the rescue and can be used from powershell. I have collected some great sources that can be taken as a reference for performing basic tasks.
- Basic opertions with CSOM (C# examples)
- Set up your environment for using the Sharepoint CSOM API
- Create a web (C# example)
- SharePoint client browser (to navigate discover, SharePoint 2013 and Office365)
- Create a SharePoint site structure with Powershell
– Added support of stats for Kitkat (due to major changes by Google BBS now requires root on Kitkat to be fully featured)
– Added the possibility to install BBS as system app
– Recreated all icons and support for xxxhdpi densities
– Fixed alarms parsing on 4.3+
– Fixed crash from gplay crash report
Full changelog: http://better.asksven.org/bbs-changelog/
I just released BetterWifiOnOff 2.1 to Google Play.
- Added more logging about connected access point
- Updated russian translations
- Add option to leave wifi on when screen goes off but a connection is active
- Added link to donate version
- Loading application whitelist is now done asynchronously
- Added timed checks: regularly turn Wifi on (all rules apply)
- Added timestamp to logcat
- Fixed event message when user enables/disables the processing from the widget
- A better fix for detecting that the donate version is installed
- Fixed alarm “null” error leaving Wifi on
- Event log should show event the same way when power is connected of disconnected
- Implemented alternate more sophisticaled cage detection