My question is simple. My server's operating system is Windows Server 2012 r2 and all updates were made on it.
When I run the iiscrypto I couldn't find TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 cipher suite. To find this, should I use Windows server 2016 or is there another way to get it?
Microsoft has a docs page that lists all the Windows versions and their cipher suites.
First server version to support this cipher suite is indeed Windows Server 2016.
Unfortunately Windows 2012 Server doesn't support tls-ecdhe-rsa-with-aes-256-gcm-sha384 or 256/128 Ciphers.
Related
I'm unable to find anywhere online where it states that BizTalk Server 2010 is supported/not supported fully by Windows 10.
No, not even BizTalk 2013 R2 is supported on Windows 10 as can be seen at Summary of 64-bit support, operating systems and SQL Server versions supported by BizTalk Server and also
Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2 as it is not listed on either page as a supported operating system.
There is a related question about BizTalk 2013 R2 and windows 10 called BizTalk Server Configuration failing to create group. The conclusion for that is, yes you can run BizTalk 2013 R2 on Windows 10, but as per a answer and comments there it probably will not be supported by Microsoft for a Production environment and could break with updates and patches applied to the operating system.
No, not directly but that shouldn't matter because running BizTalk Server on any client OS is never the best option.
Yes, you can run BizTalk Server 2010 in a Windows Server 2008 R2 VM using Client Hyper-V. You need Windows 10 Professional or Enterprise but this would be the best way to do it even if the client OS supported it directly.
I'm trying to configure a BizTalk server in BizTalk Server 2013 R2. I'm using Windows 10 and a local DB.
I can create the Enterprise SSO and the Business Rule Engine but not the BizTalk Server Group and the BizTalk Runtime.
It gives me the following error:
Failed to read "Software\Microsoft\BizTalk Server\3.0\Administration" from the registry.
The network path was not found.
I've tried everything I could imagine, any ideas as why I can't create the group?
EDIT: After trying everything I could imagine, the problem was in the name of my machine that was too big. Because of that, BizTalk could not write in the registry.
BizTalk Server 2013 R2 is not supported on Windows 10.
You can look this up in the official BizTalk Server documentation, which you can find here: https://msdn.microsoft.com/en-us/library/jj248697.aspx
Supported for BizTalk Server 2013 R2 are: Windows Server 2012 R2, Windows Server 2012, Windows 8.1 and Windows 7 SP1.
Windows 10 is not supported.
After trying everything I've searched on the web, I finally managed to solved the problem.
Because my machine name was too long (15 characters), BizTalk could not edit the registry. After changing it to 4 characters long, I solved the problem and I was able configure the server.
I would like to install a Salt minion on Windows Server 2012 R2 (64 bit).
In documentation (http://docs.saltstack.com/en/latest/topics/installation/windows.html)
I have found that 64 bit version is tested on Windows 7 64bit and Windows Server 2008R2 64bit.
Has anyone been experiencing any issues with minion on Windows Server 2012 R2?
Note: I posted this question on SaltStack user group, but no answers were provided.
Thank you in advance!
We have users on Windows Server 2012 R2. There have been no reported issues that are 2012 R2 specific.
I always recommend testing before pushing to production, though!
I am using Windows 7 (x64bit) Ultimate.
I have both ODBC32 and ODBC64 Managers that I can access via Start.
The default appears to be the ODBC64.
However I do not see MSDASQL -Microsoft OLEDB for ODBC listed.
I wonder if it exists. I see some references to 64Bit MSDASQL for Windows Server 2003.
The IBM 64bit for ODBC seems to work (I heard) but not tried.
Now I would like to know if any one knows the link for 64-bit MSDASQL for Windows 7. Microsoft seems to have deprecated MSDASQL and I am not sure of the status of this story.
These issues came up while setting up a linked server in SQL Server 2012 for SQL (SAP) SqlAnywhere server.
I am not sure how I missed. This link allows you to download the Microsoft Access Database Engine 2010 Redistributable
http://www.microsoft.com/en-us/download/details.aspx?id=13255
The details of this indicates both ODBC and OLEDB as copied from the Microsoft Web Site:
"This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and .accdb) files and Microsoft Office Excel 2010 (.xls, *.xlsx, and *.xlsb) files to other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats. "
There is no MSDASQL x64 bit for Windows 7. There is one for Windows Server 2003. I finally was able to create a linked server in SQL Server 2012 Express using the SAOLEDB.16 from Sybase/SAP.
Although I replied myself that there is no MSDASQL(x64)based on some 'deprecated items' information I am still looking at it.
Here is a link to the same question on MSDN:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/3c715023-4322-4bc6-a2c8-64a873f87e46/can-someone-confirm-the-architecture-of-this-file-preferably-microsoft-guys?forum=sqldatabaseengine#db5ed4e2-2391-4062-b34d-1f1b11431e1e
I tried creating handler for web socket but context.IsWebSocketRequest is returning always false and failed to working with IIS 8 Express on windows 7.
How can I enable module for websocket or any step I missing? I have VS 2012 application with IIS Express dynamic url.
Please help for the same.
The WebSocket protocol needs to be enabled in IIS 8 (see http://www.codeguru.com/csharp/csharp/programming-html5-web-sockets-in-asp.net-4.5.htm). Additionally, I'm not sure web sockets is supported on Windows 7. I've only seen that Windows 8 or Windows Server 2012 are required.
The short answer is, you can write applications against WebSockets in Windows 7 using IIS 8 Express, but you can't actually test them. It requires Windows 8 or Windows Server 2012.
From the IIS 8.0 Express ReadMe:
WebSocket Support
IIS 8.0 Express supports writing WebSocket applications. For more information, see the WebSocket protocol specification or the System.Net.WebSockets Namespace topic on Microsoft's MSDN website.
Windows Server 2012 and Windows 8 features that do not work on Down-Level Operating Systems
There are a few features which require architecture that is specific
to Windows Server 2012 and Windows 8 Client that will not work
down-level when you install IIS 8.0 Express on earlier operating
systems:
Server Name Indication (SNI)
Central Certificate Store
WebSocket Functionality
Then, from the System.Net.WebSockets MSDN entry (emphasis mine):
Some of the classes in the System.Net.WebSockets namespace are supported on Windows 7, Windows Vista SP2, and Windows Server 2008. However, the only public implementations of client and server WebSockets are supported on Windows 8 and Windows Server 2012. The classes and class elements in the System.Net.WebSockets namespace that are supported on Windows 7, Windows Vista SP2, and Windows Server 2008 are abstract classes. This allows an application developer to inherit and extend these abstract classes with an actual implementation of client WebSockets.