ICTCity

Hi, So, if you have 1 dc you will have less problem. First of all be sure that the object is not used by nobody (best thing is to restart the DC), when sure, rename it and wait until the resync of the DC (even if there's only one). When finished you should be able to use the new name. As you said before, the best thing is to recreate the object, I do the same thing because I'm sure it will work. If you have to rename something, follow the procedure above.

run the resultant group policy to check where's the problem. Usually there's an access denied, if so, check permissions.

check 2 things: 1) time sync, WS must be synced with DC's clock. 2) Enable the SMB signing on WS side

double thread. Closed

why do you want to connect a vpn on a LAN? that's make no sense... Anyway there's the ROUTING role in windows server for that.

you have deleted all profiles???

can you post the screen please? PS: si tu veut tu peut aussi crire en franais, aprs je fais la traduction ;)

if you really want a greate virtual-desktop experience, take a look at XenDesktop!

there's no way to accomplish this task without a cross router.

sometime it happens... no idea why...

So... create a new entry in your dns: type: SRV value: DC name where: _ldap._tcp.dc._msdcs.sasworld.com

Right click on the installer file (whatever.exe) and select RUN AS ADMINISTRATOR or RUN AS A DIFFERENT ACCOUNT. What's the username of your account?

don't confuse domain with local. You can be a domain admin but not a local admin. Login into the server and set under LOCAL ADMINISTRATORS the RDadmin account. Let me know if this helps.

open the port 88 tcp and 88 udp on your firewall

you have "many" possibilities. you can do this manually or automatically. The first thing you can do is a bonding / NIC / team solution. If you have an Intel or HP NIC you can easily bond them and this could also provide load balancing. if you want to use the routing protocol check this great article: http://networkerslog.blogspot.com/2011/04/network-redundancy-for-windows-server.html The best solution is a cross router, that means it knows if the other router fails... but they cost soo much. There are others routing protocols you can use to achieve that, but they're not reliable.

sometime this policy doesn't work. http://support.microsoft.com/kb/977944

hi, If you haven't any idea on what to do... you should ask your teacher to explain again because these 3 questions are "self answered". Anyway... 1) Type the HTTP URL of the WSUS server in both boxes. For example, type http://server1:8530 you must check your address, I don't know your :) 2) http://technet.microsoft.com/en-us/library/cc759721(v=ws.10).aspx 3) disable the local administrator account...

On a DC you don't have local users and groups, you must use Active directory users and computers

unlucky since windows server 2000 you can't do this, this is a feature that most administrator would have but actually Microsoft says that it's not possible now.

Actually it's not hard to learn... but pay attention at the word SCRIPT. C and C++ are used to create programs to interact with something (usually from user to a DB / service / ...) scripts are used to AUTOMATE something. Let's make an example: I can create a batch file (file.bat) which erase all the temporary files once the user log off. This will take 3 mins, create the file with the notepad, create a new scheduled taks, FINISH. You can do the same thing with C or C++ but you need the compiler, write the program, compile, eventualy add the required DLLs and finally add it to the scheduled tasks. As you can see everything depends on what you need to do. I hope I've ansered to your questions.

Hi, Your question is pretty easy but not the answer. Everything depends on how much traffic do you have. If you have 10 different location with 50 computers that authenticate at the same time, the speed will be really important. You can create 2 DC on the "primary" office with one domain and 10 sub-domains, then with a router or server you can create a VPN to authenticate users. The second possibility is a dedicated server for each location. With the first solution you have a centralized environment, but if something fails, everything fails. The second solution is a bit expensive but more reliable because of each location has its own server. I don't suggest you to pass directly via your ISP, it will be expensive and I don't really thing you need this at all. If you need more infos please tell me something more on what you want to do and how much location / pc / traffic you have.

run a resultant group policy to specific user to see IF the the policy has been applied or not. Sometime changing permissions screws everything up.

CreAte a sub domain into the main domain. Something like: my.work.domain and inside my.work.domain.home

Use the task scheduler ;)

Once the disk has been mapped (network disk) it's shown as a disk with its space...