RDS & network printers best practices

We are in the process of designing a multi site remote desktop solution for a customer, they have around 80 users with 5-10 users per site. I've been searching for some recommendations about the best way to deploy their network printers.
The RDS farm is located in a single site, the other remote sites will not have a local server. Traditionally we've used site-site VPN's and just set the printers up as network printers on a central file/print server. Doing this works but you lose the benefits
of Easy Print and potentially we may struggle with bandwidth at some sites.
Is there a better way to do this? One train of thought is to add the printers locally to the thin clients, then use individual printer redirection so that it utilises Easy Print. This seems to work but from a management point of view it's pretty unfriendly.
Any other suggestions?
Thanks
Robert Grigsby

Hi Robert,
Thank you for your posting in Windows Server Forum.
Please check the answer by Clarence Zhang for some basic suggestion.
RDS printing best practices
http://social.technet.microsoft.com/Forums/en-US/4dc0e050-a6ca-42d3-86f6-17babc3003fe/rds-printing-best-practices?forum=winserverTS
WS2008: Terminal Services Printing
http://blogs.technet.com/b/askperf/archive/2008/02/17/ws2008-terminal-services-printing.aspx
Hope it helps!
Thanks,
Dharmesh

Similar Messages

Network Services Best Practices

Hello
I've been using the Network Services Best Practices document (27 Sep 2006) for some years now and I wonder if there has been actually an update to it. If not would you guys have any new Network Best Practices document you would suggest? Something that talks about Virutalization, etc.... would be great

Hi Scott,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Justin Gu

IP over Infiniband network configuration best practices

Hi EEC Team,
A question I've been asked a few times, do we have any best practices or ideas on how best to implement the IPoIB network?
Should it be Class B or C?
Also, what are your thoughts in regards to the netmask, if we use /24 it doesn't give us the ability to visually separate two different racks (ie Exalogic / Exadata), whereas netmask /23, we can do something like:
Exalogic : 192.168.*10*.0
Exadata : 192.168.*11*.0
While still being on the same subnet.
Your thoughts?
Gavin

I think it depends on a couple of factors, such as the following:
a) How many racks will be connected together on the same IPoIB fabric
b) What rack configuration do you have today, and do you foresee any expansion in the future - it is possible that you will move from a purely physical environment to a virtual environment, and you should consider the number of virtual hosts and their IP requirements when choosing a subnet mask.
Class C (/24) with 256 IP values is a good start. However, you may want to choose a mask of length 23 or even 22 to ensure that you have enough IPs for running the required number of WLS, OHS, Coherence Server instances on two or more compute nodes assigned to a department for running its application.
In general, when setting a net mask, it is always important that you consider such growth projections and possibilities.
By the way, in my view, Exalogic and Exadata need not be in the same IP subnet, especially if you want to separate application traffic from database traffic. Of course, they can be separated by VLANs too.
Hope this helps.
Thanks
Guru

Cisco Network 2009 - Best practices for migrating previous versions of cisco unified communications manager to cucm 7.1

Does anybody have a copy of the above referenced presentation that you could send me.
Thanks in advanced.
The presentation can be purchased at the following site:
http://www.scribd.com/doc/33211957/BRKVVT-2011-Best-Practices-for-Migrating-Previous-Versions-of-Cisco-Unified-Communications#archive
but felt I ask one of my peeps first.
Thanks in advanced.
Dennis

Hi Dennis,
Well..let's give this a try
Cheers!
Rob

Network home best practice

We are setting up a new network of iMacs and laptops to use Network Home directories. All stations will be running 10.9 and the server will be 10.9 with Server.app 3.1. We have it currently set up, but the sync is not working. We keep having issues every 20 minutes or so and people are having issues saving permissions. We have them set up as SMB for homes. Would we do better with AFP? Any permissions that I might have wrong for the folder that the homes are being saved to?

In theory using SMB for Mavericks clients should be faster. Apple have had teething problems with SMB support in Mavericks and it is still not clear it is stable enough yet.
For laptops you would not want pure network home directories which are stored only on the server, you would want what at least used to be called portable home directories. With this the account and home directory are still stored on a server but are synced to the computer, this allows the computer to use the files even when it has no connection to the server e.g. when out of the office. When back in the office it will then sync the changes back to the server.
It used to be that you would define whether a computer was to use a pure network home directory or a portable home directory via managed preferences in Workgroup Manager. You would create a computer group to define those you wanted to have portable home directories, add the computer to the group and any user of that computer would then have their home directory synced as a portable home directory. Now with Mavericks you need to do the samething but you have to set it up via Profile Manager. You enrol the computer in to Profile Manager add it to a device group and set the device group to again sync the home directories.

Guest Network Printing - Best Practices?

I've installed a new 5th Generation Airport Extreme and turned on the Guest Network option.
After trying to get my network printer working when logged into the Guest Network, I came to this Support Forum to figure out what I was doing wrong.   Thanks to the expertise of a number of forum members, especially Bob Timmons, I learned that network printing from the Guest Network is not supported via the Airport Express and Airport Utility.
Now, with that said and understood: what are the options for printing when logged in to the Guest Network?   As I see them:
1. Emailing files/USB stick swapping
2. Moving the Guest computer to a a printer and connecting directly via USB cable
Are there other options that I'm overlooking?
Any and all thoughts on this are welcomed.

Thanks Bob,
It's taken me a few months and a change of ISPs (from ATT to Charter) but I'm back on this now.
I did buy a wireless HP printer with wireless interface.    I've attached it to the 5th Generation Airport Extreme Guest Network SSID, but cannot get a computer also connected to the Guest Network SSID to print or even see the HP printer. This includes a Mac with OSX Lion, New iPad, iPhone 4s, and company Dell running Windows 7.    I've even tried to add the the printer via IP address manually both to the Mac and the Dell to no avail; even with the specific IP address the error msg says the printer isn't detected on the network.
When I connect to the 5th Generation Airport Extreme normally (not the Guest Network) all is well and printing is no issue on any of these computers, including the Dell (which is actually the one that will be dedicated to the Guest Network / HP wireless printer on the Guest Network.
I suspect there's some very key fact I'm not aware of, and hoping that you know exactly why this is not working.
Many thanks in advance.

10Gb Networking best practices

I'm looking for good guidance on Hyper-V 2012 R2 network configuration best practices for a converged server. Meaning, dual 10Gb NICs and using SMB 3.0 file shares for storage. The servers also have two 1Gb NICs. I'm very familiar with VMware, but ramping
up on HV networking best practices.
Blog: www.derekseaman.com, VMware vExpert 2012/2013

Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

RD Session Host lock down best practice document

Hello,
I am currently working on deploying an RDS Farm. My farm has several RD Session host servers. Today I learned that you can do some bad things to the RD Session hosts, if a user presses
CTRL + Alt + End when having a open session. I locked all of this down using different GPOs which include disabled access task manager, cmd, locking the server, reboot and shutdown etc.
However, this being sad how would I know what else to lock down since I am new to this topic. I tried to find some Microsoft document about best practices what should be locked down but I wasn’t
successful and unfortunately a search in the forum did not bring up anything else.
With all the different features and option Windows Server 2008 R2 has I do not even know where to start.
Can some please point me into the right direction.
Thank you
Marcus

Hi,
The RD Session host lock down best practices of each business is different, every enterprise admin can only to find the most suitable for their own solutions based on their IT infrastructure.
I collected some resource info for you.
Remote Desktop Services: Frequently Asked Questions
http://www.microsoft.com/windowsserver2008/en/us/rds-faq.aspx
Best Practices Analyzer for Remote Desktop Services
http://technet.microsoft.com/en-us/library/dd391873(WS.10).aspx
Remote Desktop Session Host Capacity Planning for 2008 R2
http://www.microsoft.com/downloads/details.aspx?FamilyID=CA837962-4128-4680-B1C0-AD0985939063&displaylang=en
RDS Hardware Sizing and Capacity Planning Guidance.
http://blogs.technet.com/iftekhar/archive/2010/02/10/rds-hardware-sizing-and-capacity-planning-guidance.aspx
Technical Overview of Windows Server® 2008 R2 Remote Desktop Services
http://download.microsoft.com/download/5/B/D/5BD5C253-4259-428B-A3E4-1F9C3D803074/TDM%20RDS%20Whitepaper_RC.docx
Remote Desktop Load Simulation Tools
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c3f5f040-ab7b-4ec6-9ed3-1698105510ad
Hope this helps.
Technology changes life……

Best practices to share 4 printers on small network running Server 2008 R2 Standard (service pack 1)

Hello,
I'm a new IT admin at a small company (10-12 PCs running Windows 7 or 8) which has 4 printers. I'd like to install the printers either connected to the server or as wireless printers (1 is old enough to require
a USB connection to a PC, no network capability), such that every PC has access to each printer.
Don't worry about the USB printer - I know it's not the best way to share a printer, but it's not a critical printer; I just want it available when its PC is on.
I've read a lot about the best way to set up printers, including stuff about group policy and print server, but I am not a network administrator, and I don't really understand any of it. I'd just like to install
the drivers on the server or something, and then share them. Right now all the printers do something a little different: one is on a WSD port, two has a little "shared" icon, one has the icon but also a "network" icon... it's very confusing.
Can anyone help me with a basic setup that I can do for each printer?
p.s. they all have a reserved IP address.
Thanks,
Laura

may need to set print server... maybe helpful.
http://www.techiwarehouse.com/engine/9aa10a93/How-to-Share-Printer-in-Windows-Server-2008-R2
http://blogs.technet.com/b/yongrhee/archive/2009/09/14/best-practices-on-deploying-a-microsoft-windows-server-2008-windows-server-2008-r2-print-server.aspx
http://joeit.wordpress.com/2011/06/08/how-do-i-share-a-printer-from-ws2008-r2-to-x86-clients-or-all-printers-should-die-in-a-fire/
Best,
Howtodo

Best practice for RDGW placement in RDS 2012 R2 deployment

Hi,
I have been setting up a RDS 2012 R2 farm deployment and the time has come for setting up the RDGW servers. I have a farm with 4 SH servers, 2 WA servers, 2 CB servers and 1 LS.
Farm works great for LAN and VPN users.
Now i want to add two domain joined RDGW servers.
The question is; I've read a lot on technet and different sites about how to set the thing up, but no one mentions any best practices for where to place them.
Should i:
- set up WAP in my DMZ with ADFS in LAN, then place the RDGW in the LAN and reverse proxy in
- place RDGW in the DMZ, opening all those required ports into the LAN
- place the RDGW in the LAN, then port forward port 443 into it from internet
Any help is greatly appreciated.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights

Hi,
The deployment is totally depends on your & company requirements as many things to taken care such as Hardware, Network, Security and other related stuff. Personally to setup RD Gateway server I would not prefer you to select 1st option. But as per my research,
for best result you can use option 2 (To place RDG server in DMZ and then allowed the required ports). Because by doing so outside network can’t directly connect to your internal server and it’s difficult to break the network by any attackers. A perimeter
network (DMZ) is a small network that is set up separately from an organization's private network and the Internet. In a network, the hosts most vulnerable to attack are those that provide services to users outside of the LAN, such as e-mail, web, RD Gateway,
RD Web Access and DNS servers. Because of the increased potential of these hosts being compromised, they are placed into their own sub-network called a perimeter network in order to protect the rest of the network if an intruder were to succeed. You can refer
beneath article for more information.
RD Gateway deployment in a perimeter network & Firewall rules
http://blogs.msdn.com/b/rds/archive/2009/07/31/rd-gateway-deployment-in-a-perimeter-network-firewall-rules.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

RDS Gateway Best practices Dual-Homed?

Good Day,
I am wondering what is a typical amount of time others see when end users launch a RemoteApp session that goes through the RDS Gateway.
Our two RDS Gateway servers (entire environment is W2k12R2) seem slow to me. They are both Dual-Homed and with a Nic on the DMZ and Internal side of the network. Maybe I would be better off disabling the Internal Nics and reconfiguring the firewall rules
so that everything routes through the DMZ nic?
Steve J.

Hi Steve,
Thank you for posting in Windows Server Forum.
Best practice for any server is depends on your environment scenario as you need to decide whether to place the gateway in DMZ or allow 443 to be opened to the internal network. Placing the RDS Gateway in DMZ is more secure, you can have more information from
beneath article.
RD Gateway deployment in a perimeter network & Firewall rules
http://blogs.msdn.com/b/rds/archive/2009/07/31/rd-gateway-deployment-in-a-perimeter-network-firewall-rules.aspx
For more detail and understand RD Gateway refer this article.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Best practices for setting up users on a small office network?

Hello,
I am setting up a small office and am wondering what the best practices/steps are to setup/manage the admin, user logins and sharing privileges for the below setup:
Users: 5 users on new iMacs (x3) and upgraded G4s (x2)
Video Editing Suite: Want to connect a new iMac and a Mac Pro, on an open login (multiple users)
All machines are to be able to connect to the network, peripherals and external hard drive. Also, I would like to setup drop boxes as well to easily share files between the computers (I was thinking of using the external harddrive for this).
Thank you,

Hi,
Thanks for your posting.
When you install AD DS in the hub or staging site, disconnect the installed domain controller, and then ship the computer to the remote site, you are disconnecting a viable domain controller from the replication topology.
For more and detail information, please refer to:
Best Practices for Adding Domain Controllers in Remote Sites
http://technet.microsoft.com/en-us/library/cc794962(v=ws.10).aspx
Regards.
Vivian Wang

Best practice for integrating a 3 point metro-e in to our network.

Hello,
We have just started to integrate a new 3 point metro-e wan connection to our main school office. We are moving from point to point T-1?s to 10 MB metro-e. At the main office we have a 50 MB going out to 3 other sites at 10 MB each. For two of the remote sites we have purchase new routers ? which should be straight up configurations. We are having an issue connecting the main office with the 3rd site.
At the main office we have a Catalyst 4006 and at the 3rd site we are trying to connect to a catalyst 4503.
I have attached configurations from both the main office and 3rd remote site as well as a basic diagram of how everything physically connects. These configurations are not working ? we feel that it is a gateway type problem ? but have reached no great solutions. We have tried posting to a different forum ? but so far unable to find the a solution that helps.
The problem I am having is on the remote side. I can reach the remote catalyst from the main site, but I cannot reach the devices on the other side of the remote catalyst however the remote catalyst can see devices on it's side as well as devices at the main site.
We have also tried trunking the ports on both sides and using encapsulation dot10q ? but when we do this the 3rd site is able to pick up a DHCP address from the main office ? and we do not feel that is correct. But it works ? is this not causing a large broad cast domain?
If you have any questions or need further configuration data please let me know.
The previous connection was a T1 connection through a 2620 but this is not compatible with metro-e so we are trying to connect directly through the catalysts.
The other two connection points will be connecting through cisco routers that are compatible with metro-e so i don't think I'll have problems with those sites.
Any and all help is greatly welcome ? as this is our 1st metro e project and want to make sure we are following best practices for this type of integration.
Thank you in advance for your help.
Jeff

Jeff, form your config it seems you main site and remote site are not adjacent in eigrp.
Try adding a network statement for the 171.0 link and form a neighbourship between main and remote site for the L3 routing to work.
Upon this you should be able to reach the remote site hosts.
HTH-Cheers,
Swaroop

Best Practices when replacing 2003 server R2 with a new domainname and server 2012 r2 on same lan network

I have a small office (10 computers with five users) that have a Windows 2003 server that has a corrupted AD. Their 2003 server R2 is essentially a file server and provides authentication. They purchased a new Dell 2012 R2 server.
It seems easier to me to just create a new domain (using their public domain name).
But I need as little office downtime. as possible . Therefore I would like to promote this server to its new domain on the same lan as the current domain server. I plan to manually replicate the users and folder permissions. Once done, I plan to
remove the old server from the network and join the office computers to the new domain.
They also they are also running a legacy application that will require some tweaking by another tech. I have been hoping to prep the new domain prior to new legacy tech arriving. That is why I would like both domain to co-exist temporarily. I have read
that the major issues involved in this kind of temporary configuration will then be related to setting up dns. They are using the firewall to provide dhcp.
Are there any best practices documents for this situation?
Or is there a better or simpler strategy?
Gary Metz

I followed below two links. I think it should be the same even though the links are 2008 R2 migration steps.
http://kpytko.pl/active-directory-domain-services/adding-first-windows-server-2008-r2-domain-controller-within-windows-2003-network/
http://blog.zwiegnet.com/windows-server/migrate-server-2003-to-2008r2-active-directory-and-fsmo-roles/
Hope this help!

Networking "best practice" for setting up a farm

Hi all.
We would like to set an OracleVM farm, and I have a question about "best practice" for
configuring the network. Some background:
- The hardware I have is comprised of machines with 4 gig-eth NICs each.
- The storage will be coming primarily from a backend NAS appliance (Netapp, FWIW).
- We have already allocated a separate VLAN for management.
- We would like to have HA capable VMs using OCFS2 (on top of NFS.)
I'm trying to decide between 2 possible configurations. The first would keep physical separation
between the mgt/storage networks and the DomU networks. The second would just trunk
everything together across all 4 NICs, something like:
Config 1:
- eth0 - management/cluster-interconnect
- eth1 - storage
- eth2/eth3 => bond0 - 8021q trunked, bonded interfaces for DomUs
Config 2:
- eth0/1/2/3 => bond0
Do people have experience or recommendation about the best configuration?
I'm attracted to the first option (perhaps naively) because CI/storage would benefit
from dedicated bandwidth and this configuration might also be more secure.
Regards,
Robert.

user1070509 wrote:
Option #4 (802.3ad) looks promising, but I don't know if this can be made to work across
separate switches.It can, if your switches support cross-switch trunking. Essentially, 802.3ad (also known as LACP or EtherChannel on Cisco devices) requires your switch to be properly configured to allow trunking across the interfaces used for the bond. I know that the high-end Cisco and Juniper switches do support LACP across multiple switches. In the Cisco world, this is called MEC (Multichassis EtherChannel).
If you're using low-end commodity-grade gear, you'll probably need to use active/passive bonds if you want to span switches. Alternatively, you could use one of the balance algorithms for some bandwitch increase. You'd have to run your own testing to determine which algorithm is best suited for your workload.
The Linux Foundation's Net:Bonding article has some great information on bonding in general, particularly on the various bonding methods for high availability:
http://www.linuxfoundation.org/en/Net:Bonding

RDS & network printers best practices

Similar Messages

Maybe you are looking for