I have an application which I want to publish using Remote App in Windows Sever 2012 R2.
I did some research and was able to setup everything in a test Win Server 2012 R2 hosted in Google Cloud. Right now, I can access remote apps like paint, notepad etc. which I added to test the things.
https://windows-server-2012-r2-1.cloudsentinelsstudio.com/RDWeb/
But I am confused and have no idea if I need any Licenses for publishing another app for 30 users to access it from different locations.
Please help me.Thanks.
Refer to :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/d6463a27-0d4f-4eb5-ae72-43ad23811858/confused-about-rds-cals-and-other-cals-and-what-exactly-i-need-for-publishing-remote-apps-for-30?forum=winserverTS
https://www.petri.com/forums/forum/server-operating-systems/windows-server-2012-2012-r2/494633-publishing-remote-apps-for-30-users
and bottom line is in my case I would need RDS CALs for 30 users.
Related
I am developing a report in PowerBI Desktop based on data hosted in an Azure SQL Server VM.
When publishing a report, I get the below error:
Publishing succeeded, but the published report cannot connect to the
data source because we were unable to find a gateway. Please install
and configure an enterprise gateway
I believe this is because the enterprise gateway is installed locally on my azure VM, however I'm accessing it from my desktop by going over the web and through the firewall. Therefore I believe the issue is that my pc acceses the machine at
mymachine.cloudapp.net
Whilst the enterprise gateway knows the machine as
netbios-name
Is there any way that I can upload a desktop report to powerBI web using this configuration? The other solution would be to get the machine and sql server to identify itself as "mymachine.cloudapp.net" so that I can use this as the name to connect to through the enterprise gateway, but I'm not sure how to do that (adding the alias to SQL Server isn't enough).
It's a bit hacky, but I've got a work around.
Open the server and edit your hosts file and add the following line:
127.0.0.1 mymachine.cloudapp.net
Make sure that mymachine.cloudapp.net has been configured in SQL Server as an alias.
In PowerBI, add a new enterprise gateway data source, this time, use mymachine.cloudapp.net to connect rather than netbios-name. You will need to use SQL Authentication to connect.
Obviously connecting PowerBI to an Azure VM in this way is not ideal, as it could potentially be unencrypted, but this works around the issue of different host names between PowerBI Desktop and Web.
We operate a small retail business with three retail shops. Each shop has it's own PC running Windows 10 and Office 2016 (we subscribe to Office 365 Home edition). We have created a customer ordering database in Access 2016 and now wish all three shops to have access to this (add records etc) We have tried splitting the database and putting the backend on OneDrive and providing the other two with the front end. Whilst this works perfectly for the shop that split the database it is not available to the other two. Can this be done on OneDrive or should we be looking at something like SharePoint?
It won't work. OneDrive is a file syncing service, not a file share.
Move (upsize) the backend to a server engine like SQL Server (Express) or Azure SQL, which you can access from your front end application via the internet.
I am trying to find a solution to three issues I have encountered recently relating to SQL Server 2014. I am not an expert with this stuff by any means, but I've sort of fallen into needing to learn it in my current role. I went from never using SSMS a few months ago to (Trying) to teach myself how to use SSIS and SSRS. I've made a ton of progress, but now I'm stuck actually getting everything automated the way I want it.
The biggest challenge, and root of all my problems, stems from the fact that I am not a local admin on my machine. It was great to finally get IT to install the programs, but they do not want to give me, or anyone not in IT in my company, local admin access. Apart from asking my director to try to convince them to do so, I'm hoping for some solutions that would mean I don't have to call them every day to run these programs.
My integration server is running, I've got my SSIS packages built, but I can't connect to the Integration Server through SSMS, as I am not a local admin on my machine. I've read about going through dcomcnfg settings for REMOTE access issues, but I'm worried that won't help here since I'm trying to do this from the local machine and it still doesn't work. Any ideas as to how I can change the settings so that it runs for non-admin accounts or just make it work?
SSRS: I've built a report, and want to deploy it, but I don't have access to the reporting services configuration manager either. For whatever reason my reporting server is stopped in the server configuration manager. When I click on it, it says to use reporting services config mgr to tweak settings, so a bit stuck. Appears to be the same issue - not a local admin. Again, are there any settings I can change (getting IT to log in as an admin and walking them through what to change is my only choice, essentially).
SQL Server agent appears to be the same issue...
I could probably run my reports now, but it would be so much nicer to use these programs to the full extent. Any help would be appreciated here. I tried to research as much as possible, but most solutions seem to relate to logging on myself as an admin, running things as admin, etc, and I just can't do that.
Thanks!
You do not need to be local admin on your machine, SSIS and SSAS require Windows Authentication to log on remotely to the server via SSMS and publishing anything to the server from BIDS / SSDT Visual Studio Shell also requires WinAuth, though you can work locally and then swap the package to the server via Ctrl-C, and also instead of deploying SSRS you can login directly to the report manager and upload an RDL file (report). To start and stop SQL Agent services you need Windows Authentication via SSMS (in your setup), but to view the SQL Agent you must be in the SQL Server SysAdmin role (or at a grain level SQL Agent Reader via the MSDB rights.
I recommend you attempt to not get local administrator rights and instead ask 'merely' for rights to read and write to the server drives, and to manage only the aspects of SQL Server and it's services with a domain login on the server. You will require this anyway to check ingress and egress file locations and debug production issues (unless you have FTP to the box).
You do not have access to stop or start SQL Agent from your client SSMS also because I believe you are accessing it via SQL Authentication, which is not ideal or secure. But if you do not see the agent on the bottom left of SSMS it is because you do not have rights. If you see the Agent and it is red then the service is disabled and must be started.
You will need to get direct access to the SQL box (and you do not need local admin to manage SQL Server, just a domain account with some service rights and drive rights). If your system administrators are running SQL Server under Local Admin, then they should not be managing SQL Server in the first place (see my write up hyperlinked below).
The SSRS Team at Microsoft has merged into the SharePoint team, and SharePoint 2013 wraps up all of the BI tools right into it, so that is something you should also consider if you plan on building out a BI shop at your firm, i.e. you may not have to if you already have SharePoint installed.
Good luck, don't get discouraged.
What user account would you recommend running the SQL Server Express 2008 services in a development environment?
I'm having a small issue and starting to tear my hair out unfortunately.
Please excuse me if this has been answered before but I've been searching for two days and nothing is working.
I have 2 computers, one is windows 7 which is the "Server" ( 3 administrator accounts, A,B,C)
The other windows 8.1 we'll call this "Client" (1 admin account same name as C)
The Server is running MSSQL express - 2014 with SSRS on Acc:A. I'm using the BIDS (on the server Acc:B) to create reports and deploy them onto the report server happily.
What I am needing to do is to be able to access the reports from my client pc but I cant seem to be able to find what is restricting me from accessing the reports or accessing it as a service reference in VS2013.
When I Log onto accounts (useing RDP) B,C I can access the reports server happily but I try to access the reports server from the client using "Server\C" as windows login credentials it says I don't have the privileges for the home page but I can access the Site Settings.
I have a nasty feeling this is all because I'm not running on a windows server environment with domains and such which I would rather not need to use till I deploy this (when I buy a proper server) as at the moment this is all trial and proof of concept stage.
Any help anyone can give would be absolutely amazing! Thanks
Finally managed to get it working after ages, it'll be different when I deploy it but, I simply disabled the ntlm authentication and went for windows basic authentication by doing step 4 in this documentation!
Thanks for all the help!
https://msdn.microsoft.com/en-us/library/8faf2938-b71b-4e61-a172-46da2209ff55(v=sql.110)
Please help this beginner here...
I have a SQL Server 2008 R2 running on Windows Server 2008 R2.
I have Visual Studio installed on my PC.
I created my first report and tried to deploy it. It wouldn't deploy and give me a permission error saying that my (domain) account doesn't have permission to do that. So I took the quidk and dirty way out, and made - temporarily - my account an admin in the Windows 2008 Server machine. That worked, and I was able to deploy the report.
Then I sent the URL link to my boss... but now she couldn't run it because of permissions. So I can't follow the same quick and dirty solution and make all users admins in that machine...
So the question is, where and to what should I set the permissions?
Also, I can't find IIS in that server (I tried running inetmgr from the command prompt). Is it possible that it's not running or installed and still the report runs from a browser for me? I can't find the familiar "Add/Remove Windows Components".
Thanks.
You should create a service account and run all of the reports via this account. This can be configured in the Report Configuration tools. Additionally you should add your boss as a Content Viewer/Report Viewer role in the SSRS security section. You can get to this section by navigating to the URL specified when you configured SSRS, usually http://localhost/ReportServer