Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm trying to setup a Windows 2012 Server that allows for more than 2 users to access it through remote desktop at the same time.
I know I need User/Device RDP CALs for it and I already have 4 them installed/activated and they show up on the RD Licensing Manager, I also have the Remote Desktop Services role installed.
However whenever a third user tries to connect through Remote Desktop he is asked to disconnect another user.
I saw some similar questions being asked here but no answers unfortunately.
For 2012, you need the entire environment to get close to a UI, the tool we all knew and at least like is gone. The GUI is sort of available if you have the full environment with a connection broker.
You should have gotten a grace period after setup where you could use the terminal server, but after a period it has to talk to the license server, but there's no way to tell it where the license servers is like before. You can do it with group policy - Administrative Templates\Windows Components/Remote Desktop Services/Remote Desktop Session Host/Licensing.
From there you can set the licensing mode and the licensing server. The server should then see the licenses and go back to session host and not just administrative remote desktop.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 months ago.
Improve this question
I'm stuck with this problem. I have an Azure subscription for my domain with two Azure VMs named DBServer1 and DBServer2. Each of them hosts a default SQL Server instance. DBServer1 is in the East US Azure region and contains a database named Database. DBServer2 is in the West US Azure region.
How do I configure the primary and secondary endpoints, and what availability mode I need to set?
Also Is there any reliable resource where I can find questions with answers based on Administering Microsoft Azure SQL Solutions?
You can configure the primary endpoint as TCP://DBServer1.contoso.com:5022 and the the secondary endpoint as TCP://DBServer2.contoso.com:5022.
As both DBservers are not in the same region, you need to use async commit. Otherwise delay will cause application issues.
I recommend you read through this article: https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview?view=azuresql
The biggest difference with on-prem is:
Load balancer that is needed in Azure
All nodes inside your cluster need to be a member of an availability set
I also recommend using striped volumes for your SQL files to foresee better performance: https://learn.microsoft.com/en-us/gaming/azure/game-dev-virtual-machine/striped-disks-iops
Here is the resource for practicing the Azure SQL solutions: https://www.study4exam.com/microsoft-exams
Scenario-based questions will help you understand the concepts easily.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a class called Planning and Auditing of Information Systems and I came upon a exam question that goes like this:
Why is it not recommended to use "SQL Server and Windows authentication mode" for authenticating to a Microsoft SQL database?
I searched the literature I have for this and googled it but I wasn't able to find a definitive answer for this question. Does anyone know what this question could be aiming at?
When a SQL Server instance is brought up using Mixed authentication, the "sa" logon is enabled with complete sysadmin privileges and is given a password (hopefully a very strong one). The "sa" account is a common point of attack.
A hacker with access to an instance's "sa" account not only has all the data on the compromised instance and any linked servers, he also wields the power of the service account which the instance is running under by using xp_cmdshell to call PowerShell scripts among other things. Many organizations do not follow best practices for service accounts, and they will have their entire production environment running under one or two service accounts. This makes the "sa" account a very attractive point of attack for a hacker.
Under Windows authentication, the "sa" logon is disabled. This is probably what your exam question is looking for.
Mike Walston's points are also very true.
This is just my opinion, of course, but the reason it isn't recommended is that you end up having 2 different sets of users that have to be maintained and monitored at all times. In the real world this usually ends up with one of those two groups being neglected or not properly maintained, oftentimes because the sysadmins maintain the Windows Auth users and the DBAs maintain the SQL Server users. This inconsistency can lead to security concerns, or issues where users end up with both a Windows Auth username/password and a SQL Server username/password. When deactivating users sometimes only one of the two accounts will get deactivated, leading to a possible security issue.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have ClearCase license server installed in Solaris machine which is a very old machine. So our IT department want to stop using this machine and asked us to move the ClearCase license server to somewhere else. So we have installed the Clear Case license server & license administrator in Windows machine. Now we need to move the already existing licenses(300 in number) from Solaris box to windows. Can we do so? what is the procedure to do that? One more thing is now we are supposed to use only 22 of that 300 licenses.
You can check out the procedure described in "How to move licenses to a new server".
You need to release and re-assign licenses through the Rational License Key Center you can log in there).
You will be able to assign only the number of licenses you need for the new license server.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
SSMS (SQL Server Management Studio) has saved 3 login information on my computer. However, when I tell it to remeber the 4th login info, it simply won't remember anything next time.
This means that each and every time I want to connect using that Login, I should provide user name and password, and this really sucks.
Do you know how can we manage saved login information of the login Dialog?
I filed a bug about this issue, that we can't manage that MRU list:
SSMS : Expose "Connect to Server" MRU list to users
They've fixed the issue where you had to either deal with the list you have or purge the entire thing by deleting mru.dat or SqlStudio.bin. But they haven't really made the list any more manageable. I've asked the author of a popular free add-in about extending his tool to support this functionality and he's potentially going to look into it.
In the meantime, if you really want to have many (most complain about the opposite, too many redundant entries in the list), you should just create four different registered servers, and connect to them from the Registered Servers node in Management Studio. This is much easier than trying to identify which 127.0.0.1 credentials you want to connect to - much easier to name your registered servers 127.0.0.1/login-name for much quicker recognition.
If you want to be able to identify a server and login by server name alone, then maybe you could add entries to your hosts files that all point to 127.0.0.1, but look like 'local.login1' and 'local.login2'... you should be able to save each of these connection entries separately because Management Studio will treat them all as different servers, even if they ultimately point to the same instance of SQL Server.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I have to test my product with SQL Server database. Based on the search, I know I have to get hold of Developer Edition. I need to know whether for my team of 10 to access the database for testing needs 10 CALs or 10 developer licenses?
I searched enough in the net but couldn't find a straight answer.
My test setup will be like, SQL Server Developer Edition will be installed in a Test QA machine and my team will connect to that machine to test our product with.
Thanks,
ramanr
For SQL Server 2008 Developer, Microsoft's licensing page states:
You must acquire a license for each user you permit to access or use the
software. You may install any number of copies on any number of devices for
access and use by one user to design, develop, test and demonstrate
programs. Only licensed users may access the software.
They also state:
Demonstration. In addition to the licensed user, any person that has
access to your internal network may install and use copies of the software
to demonstrate use of your programs with the software.
ISTR SQL Server 2005 is similar: i.e., one copy per developer.
In addition to Chris J's answer, the licensing also provides:
II) Additional Licensing Requirements and/or Use Rights.
User Testing. Your end users may access the software to perform acceptance tests on your programs.
Microsoft answers:
http://www.microsoft.com/sqlserver/2005/en/us/developer.aspx