While looking into purchasing MSDN licenses for a client here’s what I found:
For the US:
Now when you change the drop down from US to Australia we get these prices (given
that $AUD 1 = (approx) $USD 1
So for e.g. take a MSDN – VS.NET Test.
Aussie Dollar = $3,460 US= $2,170 which
equates to $AUD 1 = $USD 0.627
this is what happens when living in a 3rd world country. –
absolutely outrageous.
Blog Post by: Mick Badran
Published By: Bill Chesnut
I have just finished a series of BizTalk 2013 Environment Installs and was testing one of my new development environments and deploy the HelloWorld SDK Sample (issues with the samples will be covered in another blog post) and dropped a couple of sample message in and then opened the BizTalk 2013 Admin Console, clicked on the Group Hub and then click Completed instances and to my surprise nothing. I proceeded to go through my normal checks, application started, hosts started and looking in the output folder, the output message was there but still not tracking. I then looked at the ports and turned tracking on, but that should not be necessary, submitted a couple more message and still nothing in the Completed instances.
I then looked at the default pipelines to make sure tracking was turned on
I opened the PassThruReceive and the tracking was on
I then opened the XMLReceive and No Tracked Events were enable, found the cause of my missing Completed instances
I enabled the tracking on the PassThruTransmit, XMLReceive and XMLTransmit. I think submitted some more messages, I now have the Tracked events for the pipelines, still missing the ones from Orchestration, not sure whether this is a binding issue with HelloWorld SDK sample of a new default.
I opened the Tracking page on the HelloWorld Orchestration and it was turned off also, turned on Track Events and now I have what I was expecting.
Hope this helped you figure out your issues with BizTalk 2013 Tracking.
*** THIS EVENT IS CURRENTLY GOING ON WORLD WIDE even as we speak! ***
The wrap up of the day:
Saturday morning was nothing short of sensational in Sydney today, early morning sun,
bright blue skies, smell of coffee and a city that felt like it was snoozing and waking
for some playtime.
I walked into a room of curious minds, eager eyes and folks that were thinking of
possibilities in technology. This technology was Windows Azure.
We were above capacity & for the first time I would be relieved if there were
a few ’no-shows’but none happened. Even at 5pm we nearly had a full house.
Firstly I’ve got to thank – you the students for a great day, fantastic questions
and giving your precious weekend time.
Secondly the expert speakers that have huge experience in the field.
and finally all the sponsors & people that helped enable us to
bring this to you:
What were the plans for the day:
The Agenda was set to:
|
SYDNEY |
Start |
Duration |
Speaker |
|
Introductions |
9:15:00 |
15 |
|
|
Compute |
9:30:00 |
30 |
Mark |
|
SQL |
10:00:00 |
30 |
Don |
|
Lab |
10:30:00 |
60 |
|
|
Cloud |
11:30:00 |
30 |
Mick |
|
Building |
12:00:00 |
45 |
Olaf |
|
Lab |
12:45:00 |
60 |
|
|
Virtual |
1:45:00 |
30 |
Mark |
|
Connecting |
2:15:00 |
30 |
Mick |
|
Lab |
2:45:00 |
60 |
|
|
Q&A |
4:15:00 |
Some Interesting facts:
– we had 3 MVPs in the room (that I knew of)
– we had 2 Microsoft VTSPs
– a student drove 3.5hrs one way to be here with us during the day, then back to Canberra
again after class. Massive commitment.
– we all came with Azure Subscriptions ready to go.
– a student created a WebSite, Database + Worker role working in a solution together
during the day.
– Olaf has his Mobile Services demo fail (even though it worked at 10pm last night)
due to the recent Azure Portal update at 2am this morning. He did have a PlanB, the
autogenerated code from the Portal during the Mobile Services Application creation,
generates un-compilable code for now. Well done Olaf, some nice tap dancing.
(Olaf working his magic)
(looking out to the North Wing)
Thanks to Magnus a fellow Azure MVP – for setting all this up world wide and good
luck to all the other countries.
If you blog about it – then be sure to use the hashtag #globalwindowsazure.
Mick out.
Blog Post by: Mick Badran
Something that you’ve always wanted at your finger tips all the public IP ranges for
the Azure Data Centers.
http://www.microsoft.com/en-us/download/details.aspx?id=29840
<!–Below address ranges are represented using CIDR notation–>
<!–For detail on how to interpert CIDR notation refer http://en.wikipedia.org/wiki/CIDR_notation–>
<regions>
<region name=”Europe”>
<subregion name=”North Europe”>
<network>213.199.160.0/20</network>
<network>213.199.184.0/21</network>
<network>137.116.224.0/19</network>
<network>157.55.230.160/27</network>
<network>157.55.3.0/24</network>
<network>168.61.80.0/20</network>
<network>168.61.96.0/19</network>
<network>168.63.32.0/19</network>
<network>168.63.64.0/20</network>
<network>168.63.80.0/21</network>
<network>168.63.92.0/22</network>
<network>65.52.224.0/22</network>
<network>65.52.228.0/22</network>
<network>65.52.248.0/21</network>
<network>65.52.64.0/20</network>
<network>94.245.104.0/21</network>
<network>94.245.112.0/20</network>
<network>94.245.88.0/21</network>
<network>137.116.224.0/19</network>
<network>157.55.230.160/27</network>
<network>157.55.3.0/24</network>
<network>168.61.80.0/20</network>
<network>168.61.96.0/19</network>
<network>168.63.32.0/19</network>
<network>168.63.64.0/20</network>
<network>168.63.80.0/21</network>
<network>168.63.92.0/22</network>
<network>65.52.224.0/22</network>
<network>65.52.228.0/22</network>
<network>65.52.248.0/21</network>
<network>65.52.64.0/20</network>
<network>94.245.104.0/21</network>
<network>94.245.112.0/20</network>
<network>94.245.88.0/21</network>
<network>137.135.128.0/17</network>
</subregion>
<subregion name=”West Europe”>
<network>157.55.10.0/27</network>
<network>157.55.10.32/27</network>
<network>157.55.10.64/26</network>
<network>157.55.12.0/28</network>
<network>157.55.9.112/28</network>
<network>137.116.192.0/21</network>
<network>137.116.200.0/21</network>
<network>157.55.8.128/28</network>
<network>157.55.8.144/28</network>
<network>157.55.8.160/28</network>
<network>157.55.8.64/26</network>
<network>168.63.0.0/19</network>
<network>168.63.96.0/19</network>
<network>213.199.128.0/21</network>
<network>213.199.136.0/22</network>
<network>213.199.180.112/28</network>
<network>213.199.180.192/26</network>
<network>213.199.180.32/28</network>
<network>213.199.180.96/28</network>
<network>213.199.183.0/24</network>
<network>65.52.128.0/19</network>
<network>94.245.97.0/24</network>
<network>137.117.128.0/17</network>
<network>168.61.56.0/21</network>
</subregion>
</region>
<region name=”Asia”>
<subregion name=”East Asia”>
<network>111.221.64.0/22</network>
<network>111.221.69.0/25</network>
<network>137.116.160.0/20</network>
<network>168.63.128.0/19</network>
<network>168.63.192.0/19</network>
<network>207.46.67.160/27</network>
<network>207.46.67.192/27</network>
<network>207.46.72.0/26</network>
<network>207.46.77.224/28</network>
<network>207.46.87.0/24</network>
<network>207.46.89.16/28</network>
<network>207.46.95.32/27</network>
<network>65.52.160.0/19</network>
</subregion>
<subregion name=”South East Asia”>
<network>111.221.16.0/21</network>
<network>111.221.80.0/20</network>
<network>111.221.96.0/20</network>
<network>137.116.128.0/19</network>
<network>168.63.160.0/19</network>
<network>168.63.224.0/19</network>
<network>207.46.48.0/20</network>
</subregion>
</region>
<region name=”USA”>
<subregion name=”South Central US”>
<network>157.55.103.32/28</network>
<network>157.55.103.48/28</network>
<network>157.55.153.224/28</network>
<network>157.55.176.0/20</network>
<network>157.55.192.0/22</network>
<network>157.55.196.0/22</network>
<network>157.55.200.0/22</network>
<network>157.55.80.0/22</network>
<network>157.55.84.0/22</network>
<network>168.62.128.0/19</network>
<network>65.52.32.0/21</network>
<network>65.54.48.0/21</network>
<network>65.55.64.0/20</network>
<network>65.55.80.0/20</network>
<network>70.37.160.0/21</network>
<network>70.37.48.0/20</network>
<network>70.37.64.0/18</network>
</subregion>
<subregion name=”North Central US”>
<network>157.55.136.0/21</network>
<network>157.55.151.0/28</network>
<network>157.55.160.0/20</network>
<network>157.55.208.0/21</network>
<network>157.55.216.0/22</network>
<network>157.55.220.0/22</network>
<network>157.55.24.0/21</network>
<network>157.55.252.0/22</network>
<network>157.55.60.224/28</network>
<network>157.55.60.240/28</network>
<network>157.55.73.32/28</network>
<network>157.56.12.0/22</network>
<network>157.56.24.160/28</network>
<network>157.56.24.176/28</network>
<network>157.56.24.192/28</network>
<network>157.56.28.0/22</network>
<network>157.56.8.0/22</network>
<network>168.62.224.0/20</network>
<network>168.62.96.0/19</network>
<network>207.46.192.0/20</network>
<network>209.240.220.0/23</network>
<network>65.52.0.0/19</network>
<network>65.52.106.128/27</network>
<network>65.52.106.16/28</network>
<network>65.52.106.160/27</network>
<network>65.52.106.192/27</network>
<network>65.52.106.224/28</network>
<network>65.52.106.240/28</network>
<network>65.52.106.32/27</network>
<network>65.52.106.64/27</network>
<network>65.52.106.96/27</network>
<network>65.52.107.0/28</network>
<network>65.52.192.0/19</network>
<network>65.52.232.0/22</network>
<network>65.52.236.0/22</network>
<network>65.52.240.0/22</network>
<network>65.52.244.0/22</network>
<network>65.52.48.0/20</network>
<network>168.61.128.0/17</network>
</subregion>
<subregion name=”East US”>
<network>137.117.32.0/19</network>
<network>137.117.64.0/18</network>
<network>157.56.176.0/21</network>
<network>168.61.32.0/20</network>
<network>168.61.48.0/21</network>
<network>168.62.160.0/19</network>
<network>168.62.32.0/19</network>
<network>137.116.0.0/17</network>
</subregion>
<subregion name=”West US”>
<network>137.117.0.0/19</network>
<network>137.135.0.0/18</network>
<network>157.56.160.0/21</network>
<network>168.61.0.0/19</network>
<network>168.61.64.0/20</network>
<network>168.62.0.0/19</network>
<network>168.62.192.0/19</network>
<network>168.63.88.0/24</network>
</subregion>
</region>
</regions>
Blog Post by: Mick Badran
If you have ever used the Table Looping functoid in a BizTalk map, then you’re aware of its ability to take multiple inputs (whether they’re links from a source schema or other functoid outputs), and configure them as a table looping grid, so that these values can be used to create multiple nodes in the […]
Blog Post by: Tom Babiec
When troubleshooting a credentials issue in BizTalk on a file share, it turns out Windows stored password configuration was used instead of the credentials saved in BizTalk host.
Last day I was able to convince my client to use, for the first time, BAM for tracking and monitoring of specific processes. As I anticipated, 1-hour work resulted in a major impact (for better) on the people responsible for these tasks in the organization. However after I deploy my BAM Definition and tracking profile […]
Blog Post by: Sandro Pereira
Hi everyone, Who doesn’t know what is Entlib? The Microsoft Enterprise Library is a set of tools and programming libraries for the Microsoft .NET Framework. It provides an API to facilitate proven practices in core areas of programming including data access, security, logging,exception handling and others. Enterprise Library is provided as pluggable binaries and source […]
Blog Post by: Jeremy Ronk
I was asked from one of my team mates and senior colleague to do the upgrade for BizTalk server from BizTalk 2010 Dev edition to BizTalk 2013 Enterprise edition. It is very simple and easy to upgrade BizTalk 2010 Dev to BizTalk 2013 Enterprise edition. Below are the pre-requisites to do this upgrade. 1- […]
Blog Post by: shadabanwer
Windows Azure Virtual Machines are the new IaaS offering from Windows Azure that allows for Virtual Machines in the Cloud. Using Windows Azure Virtual Machines you have the ability to add additional Data Disks in addition to your core Operating System Disk to your Virtual Machines. The number of disks you can add depends on the size of your Virtual Machine and range from 1 for an Extra Small VM to 16 for an Extra Large VM.
Data disks should be used for installing all your program files used on the Virtual Machines. In general, the Cache level should be set to Read Only to ensure optimal disk performance. Each data disk can get up to 500 IOPS (Input / Output Operations per Second). So as you can see spreading things out over more Data Disks should be able to boost IO throughput.
This brings me to the main point of this post – how to add a Data Disk to a Virtual Machine. To do so, select the Virtual Machine inside the Management Portal and hover over the Attach link on the bottom. If you have a Disk available to be attached, you will see an option to Attach A Disk or Attach Empty Disk. Use the Attach Empty Dish to create a new Data Disk. If you already have an uploaded VHD and want to attach it as a Data Disk, you must first go to the DISKS tab and create a Disk for the VHD.
What can get confusing is WHY any existing disk might not be able to be added to a Virtual Machine.
I have found four reasons why an existing Disk cannot be added to a Virtual Machine and two of them are not very obvious using the Portal.
The reasons you cannot add an existing Disk include:
Have you found any other reasons you cannot attach an existing Disk?
Hope this helps someone stuck trying to add a Data Disk to a Windows Azure Virtual Machine.