I need some help. Currently we have in our company physical Windows Server 2012 R2 (its private domain controller) where we manage our Fileshare, AD DS, AD CS, Printing etc... and we're thinking about to go for cloud solution MS Azure. We use Microsoft 365 too for our company. I need some explnation how it works. If we want to go for Azure way, I need to install Azure virtual Windows Server and migrate all the data there ? I found Azure AD on Microsoft it is something different ? Thanks
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
Is Team Foundation Server 2017/2018 on premises or Azure DevOps Server 2019 on premises compatible with Oracle SSO IAM? In my company we already used Oracle SSO IAM, now we started to use Team Foundation Server 2017 update 1 on premises (we'll update to 2018 or 2019 asap). I'd like to know if TFS 2017 update 1 on premises, or next versions 2018/2019, are compatible with Oracle SSO IAM? Is there any documentation about it?
TFS only uses Active Directory authentication (NTLM//Kerberos). You can use a Personal Access Token for some CLI/API actions, but Oracle isn't going to ft into this picture at all.
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/
I'm a beginner of WP7, and I spent some time looking for solutions not only can consume
but also Insert/Update/Delete the data stored in SQL Azure.
I found a good tutorial here:
http://samidipbasu.com/2011/07/24/updating-odata-data-source-from-wp7-part-1/
However, the SQL Azure Lab no longer accepts registration.
http://www.microsoft.com/en-us/sqlazurelabs/labs/odata.aspx
So, is there any other solution for directly accessing SQL Azure in the cloud without setting up a server?
Thank you.
have a look at Windows Azure Mobile Service, that should cover the server side.
you can then access the REST-based API from Windows Phone, see Using Azure Mobile Services with Windows Phone
This question has probably less to do with actual programming and more to do with environment setup.
I'm developing an application for a Windows CE device, which will use a service hosted in Microsoft Azure. Obviously, this is all under development, and the service itself has not yet been uploaded to Azure. So I'm using the emulators provided by MS to deploy the service locally. Also, I don't think uploading the service to Azure just to debug it is a good idea, as that could net us a bill for Azure we don't yet want to pay.
Also, please note, I'm using VS2008 for the Windows CE project and VS2010 for the Azure project (thank you MS for dropping support for mobile devices -_-).
The problem is, the service seems to be accessible only via 127.0.0.1 or localhost, and if I physically connect a Windows CE device or use an emulated one, it becomes a new entity on the network, and cannot access that service any more.
How can I debug my Window CE application and have it see the service, whilst still being able to debug the service itself?
You are correct, the development fabric (the compute emulator that allows you to build an azure application and debug it locally) is only meant for local development. There are some hacks that allow you to get around that, but I wouldn't recommend it.
My recommendation would be to spin up the service in a more traditional hosting environment, at least in these early stages. You can define it as a web app just as you always would have, and get it functioning. Then, when you know its mostly complete, create a cloud service project and do an add existing to bring your web app into the cloud service solution. Once in, its a simple matter to add the web app as a web role.
From there, you can complete testing of the service in both the local and hosted azure environments as needed. This allows you to minimize your development costs while still leveraging the power of the cloud. As an upside, you also have done most of the basic work to ensure your service is compatible with multiple deployment scenarios giving you a greater degree of choice for its final production state.
OK, I don't know if this was intentional, or if I found one of the mentioned hacks, but I saw that IIS hosts the Azure site I created on port 5100, and the binding for this site is *, so it accepts all connections.
Using this I could access the service from my emulator, and I could still debug all Azure related stuff.