a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
<p>Microsoft Exchange Server 2003 released on September 28, 2003. One of the new features in Exchange Server 2003 is enhanced disaster recovery which allows administrators to bring the server online more quickly. This is done by allowing the server to send and receive mail while the message stores are being recovered from backup. Now newly released version of Exchange server is Exchange 2010 after 2007 version. Exchange server 2010 officially released on 9th November 2009. But here I will discuss about Microsoft Exchange server 2003. In a workstation most of users are use Microsoft Exchange server as mail server.<br />
<p><span><span><b>Requirement of Exchange Server 2003:</b></span></span> <span> </span>Required OS for Exchange Server2003 is Microsoft Server 2oo3. There this Server should be a domain controller. For Exchange 2003 need some protocol like <br />
<p> <br />
<p><span><span><b><span> </span><span> </span></b></span></span>1> asp.net<br />
<p><span> </span><span> </span>2> SMTP<br />
<p><span> </span>3>NMTP<br />
<p><span> </span><span> </span>4>W.W.W<br />
<p>IIS should be install in server . In hardware system should have minimum 256MB of memory<br>
<p><span><span><b>Installation of Exchange Server 2003: </b></SPAN></SPAN>There have three steps to install Microsoft Exchange Server 2003.<br>
<p><span><span>1><span> </SPAN></SPAN></SPAN>Preparation of forest<br>
<p><span><span>2><span> </SPAN></SPAN></SPAN>Preparation<span> </SPAN>of domain<br>
<p><span><span>3><span> </SPAN></SPAN></SPAN>Installation<span> </SPAN>of Exchange Server<br>
<p>To install Exchange Server you have to install the required protocol first. I have install the windows component such as IIS, ASP.NET, NNTP, W.W.W. from control panel with OS CD. Then I insert the Exchange Server Disk in CD rom drive and start the preparation of forest. I open the disk and run the forest prep from Exchange 2003 deployment tools. It will take several times to complete. After completing the forest prep I have run the Domain prep with the same procedure. The Domain prep will take also lots of time to complete. Then I have installed the exchange server by creating a new exchange organization. The total process also possible to complete from Run with command. The total job takes a huge time almost one hour or more. After installing Exchange Server I have configured it as per direction of the company. I have add users, groups, I create new administrative group. Following this process there I have done the whole job successfully. <br>
if you are using AD.
do the following:
open AD, select the user, right click on the user and select porperties.
click on the Profile tab, put in the location where you want the file to g to.
you can alway created a roaming porfile and direct the home folder to the server.
this is only effective if the user login to the network. if not, then the document will be on the local machine.
Policy stay on the server. only comes to play when the user login to the network.
Policy can not be downloaded to the local machine, unless you set up each individual porfile and download that to each machine (good luck).
create a user folder on the server.
create each login folder "PC0001","pc0002", etc............
set the user rights by right click on the folder and select properties. (you need all users name. otherwise, one of more people will not have their file on the server.
now, you need all fo the users that will be using that particular PC login, in order to create the user profile. unless you have one generic login.
right click on "my document" on each of the local machine.
redirect the path under the general tab. to where you wan the files to go to.
that will place the file where you want them to be. like you say it is machine direct, not user direct. i you want user direct, in another words, you want the user files to go to the server regardless where the user is, then you need a Domain Controller and Active Directory setup.
Thanks for the background info, this makes it easier for me to see what you need.
You need to disable your guest account if you havnt already done so.
The user is logging on with a cached version of the logon information, this is useful for when the server goes down but not in your case as you need to prevent this.
Another worrying aspect is that you allow all your users to log on using the same password. Very bad from a security aspect anyhow. It is better to change at least every 30 days. If they moan they will get used to it soon enough.
Go into group policy again and computer configuration>windows settings>security settings>local policies>security options and look for interactive logon:number of previous logons to cache - set this to 0. If the domain controller is not available and the logon info is not cached they cannot logon to domain.
Group policy can be overruled at the client end if they have admin priviledges so you may have to set this on the client pc also. But you need to test to see if it is required there. I have not used that particular policy but it should be ok just on the server. Your users dont have admin rights do they? Anyway good luck. You can set this by applying it to an OU or domain wide but if you want to target just this one pc then maybe if you put it in its own ou and apply it just there.
You need to create new policies rather than modifying the domain one and keep each policy for specific purposes so that applying them to ou's is easier, ie internet options policy, firewall policy, working hours policy etc.