How to use Windows Server 2012 and 2008 as an AWS instanace in free tier account? I am having free tier account on AWS, so can I use Windows Server as my instance?
From AWS Free Usage Tier:
AWS Free Tier (Per Month):
Elastic Compute Cloud (EC2)
750 hours of Amazon EC2 Linux t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month
750 hours of Amazon EC2 Microsoft Windows Server t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month
Note that the restriction is on the instance type -- it needs to be a t2.micro instance (but possibly also includes the older t1.micro).
When launching an Amazon EC2 instance, select an Amazon Machine Image (AMI) that says "Free tier eligible". This currently includes:
Microsoft Windows Server 2012 Base
Microsoft Windows Server 2008 R2 Base
Microsoft Windows Server 2003 R2 Base
Related
Anyone know why the below "net use" command gets varied results depending on the machine OS even though I am logged on as an admin in all cases? Fails or works based on the OS within PowerShell or Cmd whether the shell is run as Administrator or not. The share is setup in Azure File Services and can be accessed on my Win10 machine just fine using Azure PowerShell cmdlets.
# mount azure share as a drive
net use x: \\[myaccount].file.core.windows.net\davesdata /user:[myaccount] [my secondary key]
Runs fine on Server 2012
Gets “access denied” on Server 2008
Gets “path not found” on Windows 10
Azure File Storage supports the following Windows / SMB variants: Windows 7 SMB 2.1, Windows Server 2008 R2 SMB 2.1, Windows 8 SMB 3.0, Windows Server 2012 SMB 3.0, Windows Server 2012 R2 SMB 3.0 and Windows 10 SMB 3.0.
If you are connecting from a VM within the same Azure region you can connect using SMB 2.1 or SMB 3.0. If you are connecting from outside of the Azure region you need to ensure that Port 445 outbound is open. Many ISP's / corporate filewalls will block this. This wiki contains a list of ISP's that allow / disallow Port 445.
To map a drive to Azure File Storage from on-prem/outside the Azure region hosting it you need SMB 3.0 which comes with Windows 8/2012 or higher. For a machine inside Azure on the same Azure region you need SMB 2.0 or higher which comes with Windows 7/2008 or higher.
Definitely works on Windows 10 using the syntax you showed, double check for typos in the path/key or more detailed error messages in the event log. The mapped drive won't survive a reboot unless you persist the credentials.
cmdkey /add:storage_account_name.file.core.windows.net /user:storage_account_name /pass:storage_account_key
Port 445 was open on my router. It took me some time to find an additional option in the router: Netbios must be set to "allowed".
Then, Windows 10 works fine for me.
I´m having a VMware image with Windows Server 2012 installed which I´m trying to import and convert to Amazon EC2.
I´m doing it from command line, and import process to Amazon S3 is successfully, but the conversion into an EC2 instance is failing. The error message I get is unsupported Windows version (Windows Server 2012 Server Standard), which is pretty strange because that OS version seems to be supported in Amazon EC2.
Someone who has experience about this?
While you can run an Amazon provided Windows 2012 image. It is not supported by the import tools.
You can import VMware ESX and VMware Workstation VMDK images, Citrix
Xen VHD images and Microsoft Hyper-V VHD images for Windows Server
2003, Windows Server 2003 R2, Windows Server 2008 and Windows Server
2008 R2. You can export previously imported EC2 instances to VMware
ESX VMDK, VMware ESX OVA, Microsoft Hyper-V VHD or Citrix Xen VHD file
formats. We plan to support import for additional operating systems,
versions and virtualization infrastructure products in the future.
Windows Server 2012 is not supported by Amazon VM import.
Still if you are not tied to AWS by an already created infrastructure, you could try other clouds like ElasticHost, CloudSigma or Windows Azure.
I'm looking to test some of the new features in Hyper-V 2012 (v3).
Hyper-V v3 can be downloaded as a "free" version "Hyper-V Server 2012", or it can be purchased as part of Windows Server 2012 Standard or datacenter. However, as usual licensing is unclear.
On the one hand MS talk about their free edition in several (many) sites. On the other hand, when you go to the actual download site it talks about a trial. To me a trial has an expiry date so it makes me nervous.
I could use my Windows Standard 2012 license as part of my Microsoft Action Pack Subscription (MAPS), but I'm not sure what I'm actually entitled to.
So my question is:
What are the real differences between the free (trial) download of Hyper-V Server 2012 and the paid-for Windows Server Core 2012 where you have to install with a key.
Does the "trial" version actually expire?
No, Hyper-V Server 2012 doesn't expire.
Hyper-V Server is quite a bit like Server Standard Core with all of the roles except Hyper-V (and other supporting roles and features) removed.
Now, in Server 2012, you can add the full UI back to the Server Core editions, but that's not an option with Hyper-V Server 2012 - it will always just be a command-line. That also means that the typical management UI tools won't run on Hyper-V Server 2012, so you'll need a machine that you can manage it from remotely (the PowerShell cmdlets for Hyper-V actually do work on Hyper-V Server, though).
Hyper-V Server isn't really for people who want to "play around" with Hyper-V - it's really designed for people who want to boost their Hyper-V infrastructure with more physical hosts, and who want to run a very lightweight OS in the root partition, leaving the most resources available for the VMs.
If you just want to get used to Hyper-V or test some things out with it, but you don't have experience with managing Hyper-V remotely already, stick with a full version of Windows Server (or Windows 8 Pro/Enterprise x64, which also have Hyper-V).
I have a single Windows 2012 Server and trying to configure it for 2 independent purposes:
(1) DB Server MSSQL-2012
(2) VDI for about 5 clients.
I understand more or less how everything works but I'm little uncertain how the VM's should be nested into a single server. Should the Base Server manage the VDI Pools OR should a separate VM be created to manage VDI??
Base Install -- Windows 2012 Server with Hyper-V Role Enabled
(VM) - Windows 2012 Server with MSSQL
(VM) - Windows 2012 Server to Manage VDI Pool
(VM) Client VDI
(VM) Client VDI
(VM) Client VDI
The best thing to do is review Microsoft's LAB setups for various (and clearly defined) VDI scenarios. VDI QuickStart
i have installed TFS 2010 in a 2 server setup with an App Tier server and a SQL Server and am not 100% happy with the performance.
Both are running in VM's on SAN disks and have been given the following virtual hardware each:
Windows 2008 R2
1 CPU # 2.8Ghz
2gb RAM
what should i lift - neither machine is hammered but both do go up to 80% when people are doing things on them - should i add another CPU to each - usually this is now required in a VMWARE setup but i don't know if TFS 2010 takes advantage of an extra core???
thank you in advance :-)
It would appear that i am more having issues with sharepoint going cold on non-peak use projects.
By installing an IIS app warmer, i solved all my problems:
http://www.diaryofaninja.com/blog/2010/05/06/keep-your-aspnet-websites-warm-and-fast-247
I am running my app server with 2 virtual cores and 2gb of RAM and it's booming
I have the database server using 2gb RAM and a single core