Install Microsoft SQL Server Reporting Services 2017 (SSRS) on a domain controller
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have set up a Microsoft Windows Server 2012R2 and installed Microsoft SQL Server 2017 Enterprise Edition on it. In general everything works fine. The purpose of this machine is to have a single server SharePoint 2016 Development environment. I have installed similar machines very often in the past, but never with SQL Server 2017 + SSRS.
Now i wanted to install Microsoft SQL Server Reporting Services on the same machine to be able to play around with the new Reporting Services, but unfortunately i receive the following error message when executing SSRS setup:
"Installation Reporting Services on a domain controller is not supported."
Of course the message is clear! But my question is:
Is there any workaround to do this anyway, maybe with a workaround oder fix?
sql-server
edited Jan 28 at 21:57
fixer1234
19.5k145082
asked Nov 26 '17 at 7:25
STORMSTORM
1064
add a comment |
I have set up a Microsoft Windows Server 2012R2 and installed Microsoft SQL Server 2017 Enterprise Edition on it. In general everything works fine. The purpose of this machine is to have a single server SharePoint 2016 Development environment. I have installed similar machines very often in the past, but never with SQL Server 2017 + SSRS.
Now i wanted to install Microsoft SQL Server Reporting Services on the same machine to be able to play around with the new Reporting Services, but unfortunately i receive the following error message when executing SSRS setup:
"Installation Reporting Services on a domain controller is not supported."
Of course the message is clear! But my question is:
Is there any workaround to do this anyway, maybe with a workaround oder fix?
sql-server
edited Jan 28 at 21:57
fixer1234
19.5k145082
asked Nov 26 '17 at 7:25
STORMSTORM
1064
add a comment |
I have set up a Microsoft Windows Server 2012R2 and installed Microsoft SQL Server 2017 Enterprise Edition on it. In general everything works fine. The purpose of this machine is to have a single server SharePoint 2016 Development environment. I have installed similar machines very often in the past, but never with SQL Server 2017 + SSRS.
Now i wanted to install Microsoft SQL Server Reporting Services on the same machine to be able to play around with the new Reporting Services, but unfortunately i receive the following error message when executing SSRS setup:
"Installation Reporting Services on a domain controller is not supported."
Of course the message is clear! But my question is:
Is there any workaround to do this anyway, maybe with a workaround oder fix?
sql-server
edited Jan 28 at 21:57
fixer1234
19.5k145082
asked Nov 26 '17 at 7:25
STORMSTORM
1064
I have set up a Microsoft Windows Server 2012R2 and installed Microsoft SQL Server 2017 Enterprise Edition on it. In general everything works fine. The purpose of this machine is to have a single server SharePoint 2016 Development environment. I have installed similar machines very often in the past, but never with SQL Server 2017 + SSRS.
Now i wanted to install Microsoft SQL Server Reporting Services on the same machine to be able to play around with the new Reporting Services, but unfortunately i receive the following error message when executing SSRS setup:
"Installation Reporting Services on a domain controller is not supported."
Of course the message is clear! But my question is:
Is there any workaround to do this anyway, maybe with a workaround oder fix?
sql-server
sql-server
edited Jan 28 at 21:57
fixer1234
19.5k145082
asked Nov 26 '17 at 7:25
STORMSTORM
1064
edited Jan 28 at 21:57
fixer1234
19.5k145082
asked Nov 26 '17 at 7:25
STORMSTORM
1064
edited Jan 28 at 21:57
fixer1234
19.5k145082
edited Jan 28 at 21:57
fixer1234
19.5k145082
edited Jan 28 at 21:57
fixer1234
19.5k145082
19.5k145082
asked Nov 26 '17 at 7:25
STORMSTORM
1064
asked Nov 26 '17 at 7:25
STORMSTORM
1064
asked Nov 26 '17 at 7:25
STORMSTORM
1064
1064
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I wouldnt attempt it. Generally speaking, domain controllers should be left as completely stand-alone servers. The risk - even if you think its minimal - of losing a domain controller, or even one of it's FSMO roles could result in a disaster that you do not want to deal with. In the past, I admit I have made mistakes that brought entire companies to a halt. Believe me, thats not something you want to have to explain to your boss.
As for why it doesnt work, I am not 100% sure. Without any research, my gut feeling is one of the services would conflict with the DCs core services and cause an issue. Ive seen white papers from Microsoft that say "dont do this." Many times Ive seen this advice ignored, as it can be done without any hacks. However, if Microsoft prevents you from doing something, it is a very good idea to not do it.
Attempting to MacGyver a solution could work perfectly fine, but the risk is not worth the reward. Keep your DCs free of unnecessary services, like SQL Server and SSRS.
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1271801%2finstall-microsoft-sql-server-reporting-services-2017-ssrs-on-a-domain-controll%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I wouldnt attempt it. Generally speaking, domain controllers should be left as completely stand-alone servers. The risk - even if you think its minimal - of losing a domain controller, or even one of it's FSMO roles could result in a disaster that you do not want to deal with. In the past, I admit I have made mistakes that brought entire companies to a halt. Believe me, thats not something you want to have to explain to your boss.
As for why it doesnt work, I am not 100% sure. Without any research, my gut feeling is one of the services would conflict with the DCs core services and cause an issue. Ive seen white papers from Microsoft that say "dont do this." Many times Ive seen this advice ignored, as it can be done without any hacks. However, if Microsoft prevents you from doing something, it is a very good idea to not do it.
Attempting to MacGyver a solution could work perfectly fine, but the risk is not worth the reward. Keep your DCs free of unnecessary services, like SQL Server and SSRS.
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
add a comment |
I wouldnt attempt it. Generally speaking, domain controllers should be left as completely stand-alone servers. The risk - even if you think its minimal - of losing a domain controller, or even one of it's FSMO roles could result in a disaster that you do not want to deal with. In the past, I admit I have made mistakes that brought entire companies to a halt. Believe me, thats not something you want to have to explain to your boss.
As for why it doesnt work, I am not 100% sure. Without any research, my gut feeling is one of the services would conflict with the DCs core services and cause an issue. Ive seen white papers from Microsoft that say "dont do this." Many times Ive seen this advice ignored, as it can be done without any hacks. However, if Microsoft prevents you from doing something, it is a very good idea to not do it.
Attempting to MacGyver a solution could work perfectly fine, but the risk is not worth the reward. Keep your DCs free of unnecessary services, like SQL Server and SSRS.
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
add a comment |
I wouldnt attempt it. Generally speaking, domain controllers should be left as completely stand-alone servers. The risk - even if you think its minimal - of losing a domain controller, or even one of it's FSMO roles could result in a disaster that you do not want to deal with. In the past, I admit I have made mistakes that brought entire companies to a halt. Believe me, thats not something you want to have to explain to your boss.
As for why it doesnt work, I am not 100% sure. Without any research, my gut feeling is one of the services would conflict with the DCs core services and cause an issue. Ive seen white papers from Microsoft that say "dont do this." Many times Ive seen this advice ignored, as it can be done without any hacks. However, if Microsoft prevents you from doing something, it is a very good idea to not do it.
Attempting to MacGyver a solution could work perfectly fine, but the risk is not worth the reward. Keep your DCs free of unnecessary services, like SQL Server and SSRS.
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
I wouldnt attempt it. Generally speaking, domain controllers should be left as completely stand-alone servers. The risk - even if you think its minimal - of losing a domain controller, or even one of it's FSMO roles could result in a disaster that you do not want to deal with. In the past, I admit I have made mistakes that brought entire companies to a halt. Believe me, thats not something you want to have to explain to your boss.
As for why it doesnt work, I am not 100% sure. Without any research, my gut feeling is one of the services would conflict with the DCs core services and cause an issue. Ive seen white papers from Microsoft that say "dont do this." Many times Ive seen this advice ignored, as it can be done without any hacks. However, if Microsoft prevents you from doing something, it is a very good idea to not do it.
Attempting to MacGyver a solution could work perfectly fine, but the risk is not worth the reward. Keep your DCs free of unnecessary services, like SQL Server and SSRS.
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
edited Nov 26 '17 at 7:46
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
answered Nov 26 '17 at 7:40
KeltariKeltari
51.7k18119171
51.7k18119171
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
add a comment |
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
First thanks for the advice and of course in general i would definitely agree with that 100% when would talk about an environment like production, staging or something similar. But in my case its only a development environment and playground to play around with services. In the meanwhile i have set up a second machine for the SSRS, so i wouldnt invest more time in researching of how to work around. Thank you.
– STORM
Nov 26 '17 at 16:14
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1271801%2finstall-microsoft-sql-server-reporting-services-2017-ssrs-on-a-domain-controll%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
