I'm running Windows 2012 R2 with Tiered Storage. Is there a way to prioritize files and ensure they always are located on the faster drives?
Thanks
I'm running Windows 2012 R2 with Tiered Storage. Is there a way to prioritize files and ensure they always are located on the faster drives?
Thanks
I'm adding a node to a SQL Server failover cluster. The installer throws the error "Addnode: Remote registry call failed. Unable to retrieve primary node Filestream settings" when adding node two
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
Addnode: Remote registry call failed. Unable to retrieve primary node Filestream settings
The os on the servers are Windows 2012. Any advice where to start looking?
Thanks
I recently installed Windows 2012 R2 Preview and are in need to construct a storage pool for usage with Thiered storage. And as the topic says there is no primordial storage pool in my system, this makes it impossible to set the rest up
Missing primordial
When trying to create a new pool
Is there a way to fix this?
Thanks
Im trying to figure a way to only allow a certain net, I.e 192.168.10.0, to communicate with certain ports in Windows 2008 R2 Server. The server setup is pretty simple. A single NIC facing the Internet but also able to act as DHCP for VPN clients connecting to the server.
The only way I've had this working so far is to set a rule where I block all traffic from 1.1.1.1-192.168.9.255 and 192.168.11.1-254.255.255.255. This will leave a gap for my 192.168.10.0/24 net, but surly there must be a better way to do this?
Thanks
I'm running SQL Server (2012) on a Hyper-V instance. It has plenty of resources and 25% reserved of the total resources, the VHD is placed on a very fast SSD drive for quick response times.
Every now and then when the applications that use the SQL Server haven't been accessed for a while they get the error "The wait operation timed out". When reloading or retrying to access the database it seems to have been "waken up" and is as fast as ever.
Is there any way to ensure that this soft sleep mode doesn't occur on this kind of environment?
Added
Exception Details: System.ComponentModel.Win32Exception: The wait operation timed out
I have two servers in this set up. AD and EX, the domain is called mydomain.net
When trying to install Lync 2010 on the EX server I get the following error "Not available :Failure occurred attempting to check the schema state.Please ensure Active Directory is reachable."
I can control the AD from EX, also login to it and do successful checks like
netdom query /domain:mydomain.net fsmo
...that resolves correctly
I suspect there is something fundamentally wrong with my setup, maybe Lync need a 2k8 R2 ad?
I have a Windows 2008 R2 Server which I moved to a new location last weekend. After configuring the DNS server (there is an Active directory installed as well) I get this dialog "Windows Security" every now and then, especially when trying to interface towards the Interwebs...
It has a message.
Connecting to wpad.domain.com
Now, any ideas what this is and how I can get rid of it?
I'm trying to set up a RADIUS server in Windows 2008 R2 following the guide Install Windows 2008 R2 NPS for RADIUS Authentication for Cisco Router Logins.
What I can't do is to register the RADIUS server to the Active Directory service which is located on the same server (see screenshot). I've tried to do this as both domain administrator and local administrator.
How can I fix this problem?
Got this kind of noob question i suppose. I got this very basic network setup and need help to set up some address forwarding.
As seen in my illustration below all traffic enters via the eth0 interface (85.123.32.23). The external dns is setup to direct all hosts to this ip as well.
Now, how on earth do I filter the incoming requests to each box? The Ip's are static!
My network layout:
I do not wish to solve this by assigning tons of ports etc.
In my wishful thinking something like this would be nice :)
set service nat rule 10 type destination
set service nat rule 10 inbound-interface eth0
set service nat rule 10 destination address ftp.myhost.com
set service nat rule 10 inside-address address 192.168.100.20
This way ALL traffic to the address ftp.myhost.com (at eth0) should be routed to the internal ip, 192.168.100.20.
Right, is there anyone who could point in some direction? Maybe it's wrong to use nat?
Please help me! :)
I'm trying to create a 'left client' > server < 'right client' setup but need some advice and tips.
Let's say that I have a server-daemon on the left side, like a vnc-server that connects to the middle server.
On the right side I've got a client that want to connect to the left server-daemon, but it has to be done through the middle server. I assume this should be done with some tunneling service.
The server environment is a fully featured Debian Linux or Mac OS X Server host.
Any idéas?
Thanks / Trikks