I have a instance with Windows Server 2012 R2 Standard in AWS. the instances is a m4.large and run a application for locations users.
The instances is in on-demand model.
i know that AWS gives me the license, but when i access the instances, i see a message requesting a license.
enter image description here
In the instance I have applications but I don't want to relaunch instances.
Anyone know the solution?
Related
I have spun up a Windows VM compute engine to host a software application(exe) from a 3rd party vendor.
Multiple users (>15) will need to use this application simultaneously so they will need to RDS into the VM through their user accounts.
We have set up Cloud IAP. Currently 2 users can access the VM simulatenously as is expected because the VM provides 2 RDS licenses.
We are trying to get more licenses but apparently an Azure AD is required for those licenses to work. Is there away to have more licenses without the Azure AD or without hosting a new AD on google?
I just want to be able to have >15 people simultaneously accessing the application on the server.
It is possible to configure Windows RDS without a domain, keep in mind that you need to purchase Device CAL's - User CALs can only be used in an AD environment; and you are limiting your options for high availability.Check the following links for guidance:
Deploying a RDSH Server in a Workgroup – RDS 2012 R2
Windows Server 2019 Remote Desktop Services without Domain
RDS Without Domain
We have a EC2 AMI windows server 2016 running in a VPC with a VPN connection to our office. The windows server currently does AD, DNS etc for the windows 10 desktop environment running in the office. We would like to use this server for Key Management for the windows 10 desktops. The problem we are having is the server requires a KMS Host Key (not the windows 10 KMS key) to setup the KMS service. From my understanding this needs to be a volume licensing KMS key for windows server. Where do I get this information?
I have asked this question on the AWS forum with no response.
Not to be confused with the AWS KMS product.
Log on to the Volume Licensing Service Center (VLSC).
Click License.
Click Relationship Summary.
Click License ID of the current Active License.
After the page loads, click Product Keys.
Look for a key called “Windows Srv 2016 DataCtr/Std KMS”
Microsoft Volume Licensing Service Center
The situation is:
- There is an EC2 instance with Windows Server 2012 R2, and the Administrator's password is lost.
- There is no other user accessible either.
- It is not an imported ovf instance, so there is no way to export it (or is there?).
- There is no EC2 Agent installed on the instance.
- I thought about using Offline NT Password & Registry Editor, but I don't know how to boot into it from an EC2 Instance.
What can I do to restore the password?
AWS has documented the process, but there are certain requirements:
http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ResettingAdminPassword_EC2Config.html
If you created the instance from an imported image, or don't have EC2Config running, you may be out of luck.
You can still detach the volume from the instance, associate it with another instance, mount it, and from there extract any data you may need.
I have MS Windows Server 2012 R2 running out of AWS facilities and want to watch its logs by CloudWatch.
Configuring Linux server, which is not an EC2 instance, works well as there are instructions how to install agents sending log records to CloudWatch regardless of where the server runs.
However, searching for such instructions for MS Windows server I am only able to find references for EC2Config Service, e.g. here http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/UsingConfig_WinAMI.html#UsingConfig_Install
It is possible, that I can simply install the service on "nonEC2" instance and it will work, but as the server is in production mode, I do not dare to do blind test ignoring risk of getting the server into problems.
Note, that I care about watching logs written to log files, I do not care (currently) about system log content.
It would help me if:
someone refers to positive experience with using EC2Config service on nonEC2 server
or someone proposes alternative method to get the log records into CloudWatch.
I recently installed Windows Server Service Bus 1.0 (on a Windows Server 2008 R2 machine).
That also installs "Windows Fabric" (not AppFabric).
Could not find much information on it, and googleing it I stumbled on a Lync server post (Windows Fabric is also installed by Lync Server 2013).
Definition:
"Windows Fabric is a Microsoft technology used for creating highly reliable, distributable, and scalable applications."
From the Service Bus architecture intro,it looks like Fabric is what allows for services replication, high availabilty, and fault tolerance.
Anyone knows if that can be used to host custom .NET services? Or any kind of direction would be greatly appreciated.
Thanks in advance.
Cos
I went to a talk by Mark Eisenberg on May 28th at the Microsoft NERD Center near MIT in Boston MA. The talk was mostly about the Azure Service Fabric. General consensus was that if you're using Azure from the infrastructure as a service perspective you aren't really using it.
The next step up is to use Azure naively as a platform meaning that rather than create VMs and hosting them there you're creating cloud services and web jobs and web apps and using the new Logic Api's etc...
But if you really want to build a stateful, resilient service enterprise class you'll want to go underneath the PaaS and write against the Service Fabric directly for greater control.
That's where the money is.
I did a write up on the talk and what the Azure Service Fabric is a few days ago and posted it here.
I don't actually think that Windows Fabric is open product. It is used for infrastructure purposes, and not for deploying custom services. For your custom services you have to use platform built on top of Windows Fabric, like Service Bus, Windows Server App Fabric.
I think Windows Fabric is for internal use by Windows Azure and Private Cloud for clustering, load balancing and so on.
UPDATE:
I've started developing Windows Azure application and here is what I've found.
I've added a Service role to Azure application and started it on local development machine (under Azure emulator). And my service was published in and started under Windows Fabric!
So the conclusion is: Windows Fabric is a platform for running YOUR Cloud Services.
Fabric which the name suggests in itself, is back-end.
It is no different than iSCSI or EIGRP. The main difference is that it is generic in form rather than specific like the aforementioned services/protocols.
IIS is a server service specific to web hosting.
SQL the same but database only..
fabric, applied to host fabric aware services and software.
Windows Fabric is used internal by Microsoft to building highly available, resilient and scalable services. It has been used for Service Bus, SQL Database, Document DB etc. according to this video: Building Resilient, Scalable Services with Microsoft Azure Service Fabric
Until now it has not been available for external parties but has now been announced as Service Fabric which will be available on Windows Azure and Window Server 2016.
Read more here: http://azure.microsoft.com/en-us/campaigns/service-fabric/