New Server 2012 R2 server to take over for 2008 R2 - confused about alias necessity

Hello,
Have Server 2008 R2 running in a small environment (35 users). It was time to get new hardware and it has been setup with Server 2012 R2. Already promoted to DC and running DNS. Ready to transfer FSMO roles over to the 2012 R2 server.
My concern/confusion comes here:
Users have network drives mapped to old server (i.e.
\\dc1\share)
New servername is for instance "dc2"
Do I demote dc1, remove it from the environment and create an alias named dc1 pointing to dc2, thus, networked drives and network printer shares continue to work, or is there a better way to do this?
thanks

imho just update mapped drives using gpo and that's all
if you have just one server for all stuff, don't demote old one , keep 2 servers alive (if you can, I don't know, maybe you need give old one away) and you will have redundancy. Then if you got 2 servers do DFS shares (shares will have names not bind
to servers name so you can add, replace server's with no problems and have redundancy of shared folders too)

Similar Messages

Creation of System Stored Procedure in SQL Server 2012 & SQL Server 2012 R2.

Hi all,
I am stuck at a point I am looking for a system stored procedure named 'sp_dboption' in SQL Server 2012 & R2 but could not find.
Searched for it on the net and found that, this stored procedure 'sp_dboption' is now obsolete. So I tried to copy the content of 'sp_dboption' stored procedure from SQL Server 2008 R2 and create new system stored procedure with this name 'sp_dboption' in
SQL Server 2012 but was unable to create the system stored procedure.
Can you guys please tell me how to create system stored procedure in SQL Server 2012 & SQL Server 2012 R2. The reason of why I want to achieve this is because I have used 'sp_dboption' system stored procedure in my application to create a database.
As 'sp_dbotion' stored procedure is present in SQL Server 2008 R2 I am able to create the database in SQL server 2008 R2 but not in SQL server 2012.
Can you please guide me how to create system stored procedure. I am out of luck.
Please assist me, thanks & looking for help at the earliest. Hope someone will come to the fore and help me.

Hi Vishwajeet,
If you tried to create any object in the sys schema, you will get the error below.
The specified schema name "sys" either does not exist or you do not have permission to use it.
So I am afraid creating any object in sys schema is not supported by SQL Server. Here is a similar link for your reference.
How to create table in SYS schema in SQL Server?
Though sp_dboption is not in SQL Server 2012, does creating a user-defined one with the same content in 2008 make any difference in your business? You just need to specify the fully qualified name dbname.dbo.sp_dboption.
If you are still interested in creating a system sp_dboption, you can register it with the
sp_ms_marksystemobject.
See
Creating Your Own SQL Server System Stored Procedures.
Eric Zhang
TechNet Community Support

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014

Difference between SQL SERVER 2008 & SQL SERVER 2012 & SQL SERVER 2014 ?

What sort of databases do you have OLTP? Data warehouse? What requirements do you have for High Availability?
The main features for SQL 2012/2014, as I see it:
o Support for window functions, which makes it possible to write fast queries for running totals, sliding windows etc.
o Columnstore indexes, which can speed up your data warehouse enormously. But of no interest for OLTP. Only writable in SQL 2014.
o AlwaysOn and Availability Groups, a vastly improve story for high availability and disaster recovery.
o try_convert/try_cast, you can now easily filter out values from a column which does not convert to a number. A small but essential feature.
o In memory-OLTP, a new in-memory engine in SQL 2014. This far with very limited feature set, and quite specialised.
Of the points above, the second and third require Enterprise Edition, the first and fourth are in all editions. For the last, I don't think Microsoft has announced anything yet.
There are also new stuff in the BI area, but that's out of my league.
And, oh, there is a new licensing model - which I think is holding more than one customer back.
Erland Sommarskog, SQL Server MVP, [email protected]

Sharepoint 2007 using sql server 2012 database server

We still have an old SharePoint 2007 farm that runs on SQL Server 2008 and Reporting Services 2008. I would like to migrate this app over to SQL Server 2012. From what I gather SharePoint 2007 supports SQL 2012 if you are running WSS service pack 3 and
SharePoint server service pack 3 I am already on SP3. So my question is who all here is running SharePoint 2007 on SQL 2012 and have you had any problems?

Yes I have an environment that is SPS 2007 wSP3 and SQL Server 2012, and have been doing this for 2 months. So far, no problems. There have been issies with User Profile services, but those turned out to be unrelated.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Server 2012 Print Server and DNS CNAME - setspn advice

Hi,
I am building a new Server 2012 Print server. What I would like to do is utilise a DNS CNAME when I deploy the printer, rather than its host name.
I have used 'setspn' to accomplish this, running the following command:
setspn -A HOST/<ALIAS> <hostname>
Now when I browse the alias I can see the installed printer. The problem I have is when I then deploy this via Group Policy it uses the servers host name instead, but it does work. If I manually edit
the GPO to reflect the alias name instead it does not deploy the printer. Moreover the indication on the 2012 server has gone so it does not see that it has any printers deployed.
When I browse the computers host name and try to manually install the printer it will state that it is downloading the drivers but never seems to complete. If I browse it's alias and try the same
thing I receive an error stating that it couldn't connect to the printer. The client machine in this instance is Windows 7 SP1 x64.
What am I doing wrong? Any help would be greatly appreciated.
Howard

I've been struggling with the same problem, for a Windows 2012 R2 print server.
I've added SPN entries and registry tweaks (OptionalHostnames, DisableStrictNameChecking, DnsOnWire etc.), but still couldn't connect printers using the alias, even though I could browse shares on the server, using the alias.
While not explicitly covering 2012 R2, this KB article helped me:
KB2546625.
Adding the alias to the local hosts file solved it for me.
Now, I wanted to be sure that I wasn't applying a bunch of unnecessary tweaks, so I went ahead and removed all registry tweaks (including DnsOnWire mentioned in the KB article), the SPN entry for the alias and rebooted - it still works!
In my case, maybe on Windows Server 2012 R2 in general, all that was needed was to add the alias in the local hosts file.

SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068643839
Start time:                    2012-07-31 16:23:37
End time:                      2012-07-31 16:33:32
Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
Next step for DQ:              Use the following information to resolve the error, and then try the setup process again.
Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
Next step for AS:              Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name:                  Haansi-PC
Machine processor count:       4
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2005      SQLEXPRESS           MSSQL.1
Database Engine Services                 1033                 Express Edition
9.4.5000        No
SQL Server 2005      SQLEXPRESS           MSSQL.1
SQL Server Replication                   1033                 Express Edition
9.4.5000        No
SQL Server 2005      SQLEXPRESS           MSSQL.1
SharedTools                              1033
Express Edition      9.4.5000        No
SQL Server 2005
Tools                                    1033
Express Edition      9.4.5000        No
SQL Server 2005
ToolsClient                              1033
Express Edition      9.4.5000        No
SQL Server 2005
ToolsClient\Connectivity                 1033                 Express Edition
9.4.5000        No
SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    Database Engine Services                 1033
Express Edition      10.50.1617.0    No
SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    SQL Server Replication                   1033
Express Edition      10.50.1617.0    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Express Edition
10.50.1617.0    No
SQL Server 2012
LocalDB                                  1033
Express Edition      11.0.2318.0     No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60    No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         F:\x64\setup\
Installation edition:          Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      false
AGTSVCACCOUNT:                 NT Service\SQLAgent$SS2012
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  TABULAR
ASSVCACCOUNT:                  NT Service\MSOLAP$SS2012
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Manual
ASSYSADMINACCOUNTS:            PC\Haansi
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Automatic
CLTCTLRNAME:                   <empty>
CLTRESULTDIR:                  <empty>
CLTSTARTUPTYPE:                0
CLTSVCACCOUNT:                 <empty>
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 <empty>
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    false
ENU:                           true
ERRORREPORTING:                false
FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD:                 <empty>
HELP:                          false
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SS2012
INSTANCENAME:                  SS2012
ISSVCACCOUNT:                  NT Service\MsDtsServer110
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
NPENABLED:                     0
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
ROLE:                          <empty>
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  NT Service\ReportServer$SS2012
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Manual
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT Service\MSSQL$SS2012
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           Haansi-PC\Haansi
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
TCPENABLED:                    0
UIMODE:                        Normal
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       SQL Server Data Tools
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Reporting Services - Native
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Integration Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Analysis Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       SQL Client Connectivity SDK
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htm

Please help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

Windows Server 2012 Member Server Time Sync Issue.

We are running in a situation where our Windows Server 2012 member Server not syncing the time from Domain Controller
Time Source is pointing to Local CMOS Clock.
Trying to Sync forcefully it getting the error as the computer did not resync because no time data available.
Performed unregistered the time service and registered the service same issue.
Kindly assist

Hello,
This seems not related to SQL Server but more related to IIS.
Try setting the trust level to full using the following article:
http://www.iis.net/learn/application-frameworks/scenario-build-an-aspnet-website-on-iis/configuring-step-4-configure-application-security#42
If the above does not solve the issue, please post your question on the following forum:
http://forums.iis.net/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Inline upgrade from server 2012 to server 2012r2

just wanted to see peoples experience for upgrading server 2012 to server 2012r2 on an inline upgrade? is this ok to do or a reimage is best?
thanks

Hi iworkhere,
I have a Windows Server 2012 DC and a Windows 2012 member server in my lab environment. I have upgraded them to Windows Server 2012 R2 with no issue. After upgrading, you will
have a Windows.old folder under C:\ and as there is no disk cleanup tool in Windows Server versions without the Desktop Experience feature, you may have to delete it manually if needed.
In addition, if no data needs to be kept in Windows Server 2012, you can choose either a clean installation or a upgrading. Personally, I prefer the clean installation.
Hope this helps.
Jeremy Wu
TechNet Community Support

Elevating Server 2012 to take over for a SBS machine.

Greetings everyone
Are there any special considerations or steps that need be done when elevating my BDC running Server 2012 from a PDC running SBS 2008? We are wanting to remove the SBS machine entirely as we no longer need it and could possibly be of use to one of our clients
down the road.
Thank You
Additional Info: We have already migrated Exchange to the cloud and is no longer hosted on our SBS server. The only function the SBS server has at the moment is being the PDC.
Jerry T

Hi Jerry,
If we want to migrate SBS 2008 to Windows Server 2012 standard, the following blog can be referred to as reference.
Transition from Small Business Server to Standard Windows Server
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Best regards,
Frank Shen

Windows server 2012 File Server - Corrupt Images

Hi Guys,
I migrated a windows file share from Windows server 2003 to a new virtual windows server 2012 data centre server. All appears ok except for one issue
There are numerous word docs on this file share (over 300 pages) with images in them (jpegs,pngs ) At times when users open these docs on the new server the images in them are corrupted. When a local copy of the same file is opened all appears fine. It has
happened on a few docs now but I cant pin point why this is happening. Obviously it was not happening on the 2003 server. I have no dedup turned on or compression. I simply copied the files over and ntfs permissons. It does not happen all the time so I am
thinking it is some read/write issue in 2012. The server reports no high cpu or memory at any time.
Any thoughts on this?
Thanks

Hi. Did you ever get to the bottom of this problem?
I have the exact same issue after migrating from Server 2003 to 2012. Occasionally Office files that include images stored on the share will get corrupted with the top of some of the images showing normally and then blurring or noise in the rest of them.
I can usually restore a copy of the file made by shadow copy but the corruption of images should not be happening in the first place. Some users are losing confidence in storing their work on the share which is potentially a big issue.
I am pretty convinced that this is an issue with Server 2012 as we have not migrated from Office (2010 Enterprise) and files stores on 2003 servers on or PC hard drives are not affected.
Thanks!

Hyper-V 2012 High Availability using Windows Server 2012 File Server Storage

Hi Guys,
Need your expertise regarding hyper-v high availability. We setup 2 hyper-v 2012 host in our infra for our domain consolidation project. Unfortunately, we don't have hardware storage that is said to be a requirement that we can use to create a failover cluster
for hyper-v host to implement HA. Here's the setup:
Host1
HP Proliant L380 G7
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Host2
Dell PowerEdge 2950
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Storage
Dell PowerEdge 6800
Windows Server 2012 Std
File and Storage Services installed
I'm able to configure the new feature about Shared Nothing Live Migration - i'm able to move VM's back and fort between my hosts without storage. But this is planned and proactive approach. My concern is to have my hyper-v host to become highly available in
the event of system failure. If my host1 dies, the VMs should go/move to host2 and vice versa. In setting this up, i believe i need to enable the failover clustering between my hyper-v hosts which i already did but upon validation, it says "No disks
were found on which to perform cluster validation tests." Is it possible to cluster it using just a regular windows file server? I've read about SMB 3.0 and i've configured it as well i'm able to save VMs on my file server, but i don't think that my hyper-v
hosts are already highly available.
Any feedback and suggestions or recommendation is highly appreciated. Thanks in advance!

Hi Guys,
Need your expertise regarding hyper-v high availability. We setup 2 hyper-v 2012 host in our infra for our domain consolidation project. Unfortunately, we don't have hardware storage that is said to be a requirement that we can use to create a failover cluster
for hyper-v host to implement HA. Here's the setup:
Host1
HP Proliant L380 G7
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Host2
Dell PowerEdge 2950
Windows Server 2012 Std
Hyper-V role, Failover Cluster Manager and File and Storage Services installed
Storage
Dell PowerEdge 6800
Windows Server 2012 Std
File and Storage Services installed
I'm able to configure the new feature about Shared Nothing Live Migration - i'm able to move VM's back and fort between my hosts without storage. But this is planned and proactive approach. My concern is to have my hyper-v host to become highly available in
the event of system failure. If my host1 dies, the VMs should go/move to host2 and vice versa. In setting this up, i believe i need to enable the failover clustering between my hyper-v hosts which i already did but upon validation, it says "No disks were
found on which to perform cluster validation tests." Is it possible to cluster it using just a regular windows file server? I've read about SMB 3.0 and i've configured it as well i'm able to save VMs on my file server, but i don't think that my hyper-v hosts
are already highly available.
Any feedback and suggestions or recommendation is highly appreciated. Thanks in advance!
Your shared storage is a single point of failure with this scenario so I would not consider the whole setup as a production configuration... Also setup is both slow (all I/O is travelling down the wire to storage server, running VMs from DAS is ages faster)
and expensive (third server + extra Windows license). I would think twice about what you do and either deploy a built-in VM replication technologies (Hyper-V Replica) and apps built-in clustering features that does not require shared storage (SQL Server and
Database Mirroring for example, BTW what workload do you run?) or use some third-party software creating fault tolerant shared storage from DAS or investing into physical shared storage hardware (HA one of course).
Hi VR38DETT,
Thanks for responding. The hosts will cater a domain controller (on each host), Web filtering software (Websense), Anti-Virus (McAfee ePO), WSUS and an Auditserver as of the moment. Is the Hyper-V Replica somewhat give "high availability" to VMs or Hyper-V
hosts? Also, is the cluster required in order to implement it? Haven't tried that but worth a try.

Are there any differences between Server 2012 and Server 2012 R2 that might impact TFS or SQL server required for TFS?

Hi,
In the interest of just getting started and learning the basics of setting up TFS, I previously setup an IDE using a large workstation running Windows 8. I set up the required servers for TFS using VM's through Hyper-V. I am now transferring
everything to a new and separate physical server.
My question stems from a problem I had when I originally setup the TFS system the 1st time. I couldn't get SQL server to work using the Server 2012 R2 download from the subscription center. When I used Server 2012, it worked, so I proceeded that
way just to get going.
So now I'm setting things up anew on a new physical box, I want to ask up front, is there some difference in the R2 version that causes problems with either TFS or SQL server, or was there likely some oversight on my part when I did things the 1st time?
As an addendum to my question, I always assumed R2 merely means the Server software has progressed to a refined state and is ready for wide distribution and easy setup. I assumed that there are no differences between the Standard version and the R2
version. Is that understanding correct?
Thanks.

Hi Daniel,
Thanks for your response. That's a great link. I don't recall seeing a page that is so clear and easy to read back when I was doing this the 1st time, but I probably just missed it. That helps.
I am/was using TFS2013 and VS2013. As I recall, my problem was getting SQL Server to work, but I thought asking this question on this forum was wiser because I figured everyone using TFS would be well familiar with these issues.
At any rate, it seems as though TFS2013 is fine with Server 2012 standard or R2.
I was using SQL Server 2012, and it also seems as though it works on R2:
https://msdn.microsoft.com/en-us/library/ms143506(v=sql.110).aspx
Anyway, thanks for your support. I'll be trying this again and we'll see.

SQL Server 2012 Report Server mode is blank?

Hi, I have configured SharePoint 2013 with SQL Server 2012 on Windows Server 2012
with complete features on the same server.
But when I checked Report Server mode under Report Service Configuration Manager it’s
showing blank means Report Server mode neither in native mode nor in SharePoint integrated mode.
What is the issue?
I want
Report Server mode should be in SharePoint integrated mode.

You need to install the Reporting Services - SharePoint feature from the SQL Server installation media onto the SharePoint server. You then need to start the Service Instances in Manage Services on Server and create a new SSRS Service Application in Manage
Service Applications.
http://msdn.microsoft.com/en-us/library/gg492276.aspx
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SCCM 2012 SP1 + WSUS + Server 2012 + SQL Server 2012

Hi all;
I installed SCCM 2012 with Sp1 for my site server and everything is going well.. And than i installed the WSUS role on my Windows Server 2012 and SCCM 2012 SP1 it gave an error message which is "Fatal Error: The schema version of the database is from a newer
version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database." My database server is SQL Server 2012... Do you know any pathc for WSUS or SQL Server 2012 doesnt support WSUS yet???
Thank You...
MCT

Normally if you are going to install SCCM 2012 SP1 +Windows 2012 with SQL 2012, Then you better use the SQL 2012 sp1.
also when you are installing the WSUS version 6.2 which come with server 2012 make sure you leave the default settings as it is. it shows in the below article.
also when you are giving the path to save the WSUS contents make sure the drive you going to create the wsus folder and the place where you going to download the updates is having free disk space and its formatted with the NTFS volume. Also the service account
you are using for this configuration should have the admin rights to the location of the wsus folder you going to create,
Thanks
Hasitha

In-place upgrade from Server 2012 to Server 2012 R2

I have a Dell PowerEdge 1850. I installed Server 2012 Standard. This works fine. I made it a domain controller in an existing domain. I also added Print Management Role. This was working fine.
I then did an in-place upgrade to Server 2012 R2. Now it is stuck in a rebooting loop.
It says "Your PC needs to restart. Please hold down the power button. Error Code: 0x000000C4. Parameters: 0x0000000000000091, 0x00000000000000F, 0xFFFFF803827DCA00, 0x0000000000000000.
I cannot get out of this loop. Others have said they have this problem when installing with virtualization. However, I am installing on the native hardware. The CPU does not support hardware virtualization.
This worked fine with Server 2012. In fact, I have 4 other Domain Controllers that are identical to this one running Server 2012. Did Server 2012 R2 add a CPU feature check that is hampering this?
Don Demars

The 1850 is a pretty old box. What you are running into sounds like the lack of a proper disk driver for the box (I've had that happen multiple times during new releases). The disk driver needs to be provided by Dell. I don't believe Dell
supports the 1850 with 2012 R2, so getting a driver for it might be a bit of a challenge. You can find which servers Dell supports under the different versions of Windows Server by checking out
www.windowsservercatalog.com.
Microsoft only puts supported device drivers submitted by the vendors well ahead of time on the distribution media. Seeing that you were able to get 2012 running on the 1850s earlier, my guess is that you had separate media for the driver that you
used during the installation. There is a place during the installation that allows the loading of device drivers that are not on the installation media. If you can get Dell to give you a driver for 2012 R2 for the 1850s, maybe you can update the
driver under 2012 and then update the OS.
Personally, though, I never upgrade a domain controller in place. It is so easy to simply create a new one and add it to the domain. Then, if you do have a driver for 2012 R2, you can load it during the clean installation.
. : | : . : | : . tim

New Server 2012 R2 server to take over for 2008 R2 - confused about alias necessity

Similar Messages

Maybe you are looking for