How was the share originally provided to the users? If they're connected to \\servername\sharename, then moving the share to a new server won't solve the problem of the clients pointing to the old share.
You can't control individual servers in a blade server from a console, you have to either use RDP or connect to the Management Module in the blade and then control the individual blades.
But...as Pat says if your boss installed Windows core then that complicates things. Is it responding to an...
As Pat says...boots-in-the-office days are past us...this can all be done remotely now. For a few hundred dollars you can have someone that can assess your situation and setup the new server seamlessly do it and you get to watch and ask questions and learn from what they've just done...
If you have a domain login on a notebook system, you should still be able to logon to the domain account even if you're not connected to the domain. That way as long as they save their documents locally they will still be available at home.
www.focusonthefamily.com www.townhall.com...
Unfortunately I believe it's only a problem they'll be able to resolve since it sounds like something else is wrong within the system you have.
www.focusonthefamily.com www.townhall.com www.rushlimbaugh.com www.freedom-of-religion.org
I love the smell of a dead botnet early in the morning... ;)
www.focusonthefamily.com www.townhall.com www.rushlimbaugh.com www.freedom-of-religion.org
Not doubting your capabilities, but you way want to consider hiring a consultant to come in and set it up for you along with a transfer-of-knowledge while they do it. While I was fully capable of doing my Exchange 2007 implementation, I brought someone in just to be sure and, to be honest, was...
How many servers do you have and why do you feel consolidation is the proper "next step"?
Have you done the numbers on the utilization and determined that less servers would indeed handle the current load and then some?
I'm Certifiable, not cert-ified.
It just means my answers are from...
The number of users connected to a piece of hardware is independent of the load upon that server created by the applications those users are using. It is the load upon the server caused by the number of users and the applications they are using that you should be worrying about, *not* the number...
We static ours. When we planned out the network we set aside a block of IP's for printers, servers, etc. Of course ten years later those "blocks of IP's" are full and we have carved out a different set, but the user never sees that.
I'm Certifiable, not cert-ified.
It just means my answers are...
Ditto Pat's response, to the letter.
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
There are no more PDC's! There are DC's with FSMO roles!
What are you providing to your users application wise? Just file servers? Application servers? Email? You need to tell us what your environment is.
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
There are no more PDC's! There are DC's with FSMO roles!
It's called RDP. Enable it on the server and then connect via any workstation.
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
There are no more PDC's! There are DC's with FSMO roles!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.