Tag Info

Hot answers tagged

13

10 Mb is not fast. Go ahead and set up sites. A number of manageability improvements will follow. Sites are associated with subnets, and I assume you already have separate subnets for each site as you imply that they are all associated with one WAN. If so, the implementation of sites is not time-consuming.


13

It's quite possible to have an Active Directory architecture configured across multiple physical locations in a single site. It's generally not a "good thing" and goes against most best practice. If you ever want to control/configure/optimize your replication traffic, you'll have to setup sites. If you ever want to do branch cache in a reasonable way, ...


10

Creating another domain adds complexity. To the extent that you are able to maintain a single domain environment you will limit complexity. I find that administrative activities are easier in a single domain environment. Visual organization ("a tidier organization") could be accomplished with other features, like organizational units (OUs) in Active ...


7

You don't want rewrite rules at all, you do want to setup a new website configuration. IIS 6 can differentiate between websites via either using a new IP address (so the server has multiple IP addresses), or by using a host header to link a domain to a website configuration. Try starting here: Hosting Multiple Web Sites on a Single Server (IIS 6.0) and ...


7

You don't have different DNS namespaces for the two branches if they're in the same AD domain. There's no reason to. They would both be in the same DNS namespace as the parent. What reason would you have for two different DNS namespaces? Also, avoid naming your AD domain "company.com" if that's also what your external website's name is. Name it something ...


7

There are a lot of things that use Sites and Services besides just the logon process and DC-to-DC replication traffic. Exchange uses it for global catalog location DFS-N uses it for referral target ordering DFS-R uses it for replication partner selection You can leverage site-based GPOs If you don't want to wait the minimum 15 minutes for replication ...


6

you could generate small configuration file for each directory(virtual host) you have if you need to handle those differently or if you want to save effort use the following: server { server_name ~^(www\.)?(?<domain>.+)$; location / { root /sites/$domain; } } This maps the request domain to a directory.


6

No, almost certainly not. Unless you have political pressure in terms of one administrator effectively having access to everything, then stick to one domain. There are arguments with regard to the same DNS namespace being used, which might not suit a multi-branded multinational, but sounds like this isn't an issue for you. Again, this is all bollotics. ...


5

The 'How to Scale WPMU' page you link to proposes a solution which seems like a nice solution but I question how well it will scale. What they do is fairly straight forward. They use the host name header to let the reverse proxy decide to which server to route the request. Basically they look at the first letter of the blog name and then route the request to ...


5

I think the safest thing to do is to call Microsoft Support and have them guide you through it. The thing is, doing something as simple as manually modifying the Dsa Not Writable registry entry can land you in a permanently unsupported state. With that disclaimer out of the way, the thing with USN rollbacks is that you need another DC in the domain to be ...


5

As your question is currently posed, it sounds to me like you could get as much mileage out of setting up a new Site in Active Directory as you would with a new domain. You'd create a new domain controller at the new physical location, but in the same domain and forest, and set it up to serve the new site in question (through the Active Directory Sites and ...


4

Firstoff, the Cisco 2821 is just a router. I don't know where you've gotten this "layer 2 router" business from (the statement is an oxymoron in itself), but a 2821 is a perfectly capable IP router. You don't want to extend a layer 2 broadcast domain across a VPN. You won't like how it performs. Let's call your existing location "site A" and the new ...


4

Sounds like a pretty straightforward deployment. It sounds like you've already created your domain. Since you're using SBS, be aware that the existing SBS machine will be forced to hold all the Active Directory flexible single-master roles. That's probably not a big deal, but the 75 user limit in SBS might be. While SBS makes for an attractive price-point ...


4

Yes, it is. Try defining in default.vcl your backends first: backend foo { .host = "1.2.3.4"; # IP of foo backend .port = "80"; } backend bar { .host = "1.2.3.6"; # IP of bar backend .port = "80"; } and use in vcl_recv() code similar to: if (req.http.host ~ "foo.example.com") { set req.backend = foo; }else{ set req.backend = ...


4

Promote a DC in Site B, create two sites in AD, then assign each domain controller to its appropriate site. Also, install DNS on this server, and use it as the primary for all hosts in Site B. Ideally, the hosts in site A would use the local DNS server as primary and the DNS server at the opposite site as secondary. Vice-versa for hosts in Site B.


4

The Schedule attribute is a BLOB, so setting that from PowerShell is probably going to be a bit of pain. I suspect that you can set one of your site links manually with the GUI and then use the value stored in "Schedule" to replace the "Schedule" value on other site links. I haven't tested this code, but I suspect this will work to reset the replication ...


4

Your understanding is not correct. The time for an A or CNAME record query does not depend, in any way, on how many other A or CNAME records might also point to the same IP address. The hosting company may not have enough bandwidth (or CPU, or RAM, etc) to support good response times for all clients if one of the clients is particularly popular, but that is ...


3

You could buy a reseller account and create sub-accounts for each domain. There is also the possibility of just using a regular shared hosting account with cPanel as long as the plan offered by the host supports "add-on" domains, in which case they will all sit in your public_html in their own directory.


3

To my knowlege not possible due to security constraints - you need two ip addresses. IIS tries to fowward the request to the proper sub-instance BEFORE decoding it, and it can thus not evaluate the host header via https. So, for SSL you need multiple ip addresses.


3

I don't think you can do this with IIS but it's possible with Apache using SNI (Server Name Indication extension in SSL protocol Configure Apache to support multiple SSL sites on a single IP address. The problems are on the client side: it doesn't work with IE below 7 and doensn't work on XP, even with IE 7. Vista from IE 7 is ok. No idea if it works with ...


3

None of those things are impossible. At least I don't think there are any limitations in SBS that will stop you (I haven't used SBS since SBS 2000). You'll need to provide some form of network link (such as a VPN) between the two offices, and while Windows server can do this, I'd get a couple of very cheap machines and set up a VPN between the sites using ...


3

I see no problem here. IIS 6 can host hundreds of websites - even for on the same IP address (except for https you'll need a dedicated IP address) - distinguishing them by the host header (domain name). Read this Microsoft Support article: HOW TO: Use Host Header Names to Configure Multiple Web Sites in Internet Information Services 6.0: Microsoft ...


3

Generally speaking, you should always try to have as flat a domain structure as possible, preferably a single domain. Partitioning into domains should have clear business drivers, as there are few technical reasons for "architecting" an Active Directory system this way. Multiple domains create complexity that can be daunting when issues occur. Domains ...


3

There's no need to do this. Virtualhosts exist to separate websites from each others' namespace.


3

I suspect that the documentation you're looking for is not publicly available. Arguably the "deepest" technical reference for Active Directory replication, aside from the product's source code, is [MS-DRSR]: Directory Replication Service (DRS) Remote Protocol. The attribute you're examining with WMI is the DRS_INIT_SYNC bit flag on the RepsFrom type. The ...


3

First, check if it's actually your site or a copy. Do a nslookup your_domain.com and nslookup the_other_domain.com and see if the results are the same. This is not a hack, at least not against you. More likely than not it's someone setting up for a phishing attack against your clients/customers/whatever. It's also possible that someone plans on using your ...


2

What you want to do is really not recommand. Extending a broadcast domain over a WAN is not a good idea. There is 2 way to do this. If you have layer 2 link between you site, just use a switch. But as you talk about router I guess your site are connected with layer 3 so you can use L2TP to do Layer 2 over Layer 3 (4 in fact). Please take a look to : ...


2

All you're looking for is Host Headers. As long as the host headers are different, multiple sites can share the same port. Go to the properties of the site, and under the "Advanced" button next to the IP Address binding dropdown, you can edit the port and host header(s) for the site. No more drama than that. ;)


2

You can do all this without having the users site in the email address. You simply put the users mailbox on the server at their site. Then when they send mail to a user at another site the Exchange network handles all that once there is a VPN connection between the sites. You'll need a VPN connection between the sites every once and a while to handle AD ...


2

Use a redirector. app.company.com/CLioentA gets redireted to ClientA.app.company.com. Pretty much every reverse proxy should do. It can also rewrite the HTML in the pages when needed. Pretty much the only solution I can see.



Only top voted, non community-wiki answers of a minimum length are eligible