|
- Cannot complete installation of connector software as The password is . . .
The WHS windows event log contained nothing interesting, but the Windows System event log contained several DCOM errors that coresponded with each of the Connector install attempts
- file transfer speed over GB LAN - social. microsoft. com
I have an XP MCE machine and a WHS machine connected to my GB LAN on either side of a Netgear GB switch When I first installed the switch (replacing an old 100 MB switch), I got susstained file transfer rates of 300-400 MB s from MCE to WHS Now when I transfer, for example, recorded TV files from MCE to WHS the transfer starts off fast, say 400MB s for 5 or 10 seconds then slows to nothing
- For WHS Team: WHS 2. 0 and add-in backwards compatibility
In short if you could take PP1 WHS 1 0 backups, and restore them into a shiny new 2 0 WHS, and almost everything got configured correctly, that would probably be sufficient I don't expect to see anything though that automatically redeploys add-ins
- WHS data storage on external raid HDs only. . . ?
I assume that this arrangement would be 'seen' by WHS as if only a single data HD is present The load balancing between the external HD's would be handled by the Raid controller in the array cabinet
- Is it safe to download incremental files to WHS? (eg. download . . .
I guess WHS isn't really meant for short term storage but only long-term storage I'd hate to dedicate a large hard drive to "temporary unzipping operations" but it looks like that is the only solution?
- What happens if I have 2 WHS in my network? - social. microsoft. com
I have just installed my 2nd WHS, It is the RTM version for download to test the new beta with My other server is OEM I bought after the original beta was over When I installed the connector cd it DID NOT ask what server to join It joined the new server without asking I can see them both with RDC, I have machines set up to use server1
- WHS console add-in which can run remote applications on the connected . . .
As far as I can see, the WHS console is an application running on the Server which is just displayed on the computer from which WHS console was started (using RDP)
- WHS-hosted apps: where to install, UNCs versus drive letter paths, etc.
While WHS is being (rightfully) positioned as a generic server platform for the home, one thing that hasn't been clearly stated (at least not anywhere I've seen) is guidelines for the use of WHS-local disk resources by apps running on the server
|
|
|