ICTCity

Yeah, everything right... but why they're NOT INSTALLED? This is what I can't understand...

Hi, It's quite easy, trust me! Folder redirection: let's say that you don't want yours users save their docs on their desktop, what you can do? You can ask them, but they will never stop to save docs on their desktop... so... after a month or two, they come and say: "Ehiiii my computer is so sloooow when I turn on my pc!" Then you see that the desktop folder has a size of XX Gb. To prevent this, you can easily redirect the desktop or any other folder. Just create a new redirection rule which points to DESKTOP and redirect somewhere. What I usually do is to redirect the documents and images folders to the personal disk (mapped disk for that user). Profile maps: well... where the profile will be stored. If not specified, it will be stored locally on computer. Home folder: basically is the same as the property of active directory user, you can specify the "default" disk mapped for that user. I never use home folder, I use scripts which are (for me) more flexible. To create a simple profile folder, do the following steps: 1) Create on your 2nd disk a folder called PROFILES (or whatever you want) 2) Select ALL THE USERS you want to add a profile path (SHIFT + CLICK) 3) Then on PROFILE MAPS or PROFILE PATH (depending on where are you setting this), write this: D:\Profiles\%username% Be sure to write %username% this will set the correct name for all users, otherwise you must do this manually! Now, when a user login, in D:\Profiles\ you can see a folder with the username and inside there's the profile. Almost the same thing for personal folder/disk: Create D:\PersonalFolders\ Add the property in AD for all users: D:\PersonalFolders\%username% Now you have two choices, you can manually create the personal folder (for the profile is created automatically, for the personal folder no...), or you can do this with a script, but as long as you are learing, I will not tell you how to do this... there are many examples on internet! If you need help... I'm here :) bye

Hi and welcome! I'm 21 ;) Enjoy your stay!

Hi, there's DropBox or if you want a professional (but quite expensive) solution, check Acronis, there's the cloud backup. Until 2GB is free, then you must pay.

Hi, This is a problem related to VMware... anyway... take a look at these 2 topics: http://xtravirt.com/disabling-virtual-machine-guest-host-time-synchronization-multiple-hypervisors http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1189 You CANNOT disable SyncToCmos manually, there's no option for that.

Maybe I'm wrong, but Windows Search and Indexing are not the same thing. You can install the "plug-in" Windows Search, but Indexing service is a role... Mhhh this is not the first time that I hear about a problem like this (service installed but they appear to be uninstalled)...

Ok, try this (and hope that this will fix your problem): Go to the Start menu, type services.msc and press the Enter key; Make sure the Windows Search service set to Automatic startup mode; Go to the Start menu, type regedit and press Enter; Go to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search; Change the value of SetupCompletedSuccessfully to 0 (if not, create it); Restart your computer; Start Microsoft Outlook.

mhhh that's no gooood. Try the following steps: from cmd: net stop WSearch && net start WSearch I think you will have the error: "not found" but... try it. Then open services.msc and look for Windows Search, is it present? What's its status? If you can't find anything, remove the indexing role and re-add.

To manage Indexing service, follow these steps (from MS's website): Click Start, click Run, type mmc, and then press ENTER. On the File menu, click Add/Remove Snap-in. In the Available snap-ins list, click Indexing Service, and then click Add. In the Connect to Computer dialog box, click Local computer: (the computer this console is running on), and then click Finish. To close the Add or Remove Snap-ins dialog box, click OK. The console displays the Indexing Service snap-in. Then, open a command prompt and type: sc queryex WSearch then sc interrogate WSearch And post results. thanks

http://www.howtogeek.com/howto/windows-vista/turn-on-remote-desktop-in-windows-vista/ As you can see, in the last screen there's SELECT USER. Add users you want.

Go to CONTROL PANEL, there is INDEXING OPTIONS. From there, you can add paths to index. Pay attention, do not add too much path.

If your server logs everything you can find it under EVENT LOG... but you must enable almost everything.

Via windows this is not possible. You should check this software: http://www.booleserver.com/

Mhhhh there's a problem with you NIC (server's side), I can't understand why you have a ping of 2-4 ms... is too much in a LAN.

Are you sure that the DHCP server is not behind a router and IS on the same network as the computer? Are you sure that in the scope 192.168.10.1 - 10 there are NO computers, routers, servers, ... which are using these addresses?

Sorry, my mistake... try this: shutdown /s /m

Try to map via command line using net use SHARED PATH /p:yes

And without -i?

Hi and welcome!

Check on your DHCP server if the service is running and if it has any address assigned.

Errors? messages? try this: shutdown -i -m \\IP_DC

1. Try to use a JPG instead of BMP, make sure the path for wallpaper is available and users have rights to read it. If this doesn't help, disable the active desktop and use this ADM file: CLASS USER CATEGORY "Control Panel\Desktop" KEYNAME "Control Panel\Desktop" POLICY "Wallpaper" PART "Wallpaper" EDITTEXT DEFAULT "\\server\Policy\Wallpaper\WALLPAPER.bmp" VALUENAME "Wallpaper" END PART END POLICY POLICY "WallpaperStyle" PART "WallpaperStyle" EDITTEXT DEFAULT "0" VALUENAME "WallpaperStyle" END PART END POLICY END CATEGORY 2) yes, this is right. V and V2 are only for compatibility with old system (2003). It doesn't matter :)

be sure that there's no router or firewall because usually this problem occurs when something is misconfigured. Maybe the problem is that all the network starting with 77 are considered as the server, this will block the proper communication.

Most policies, when opened, have 2 tabs. One is to enable or disable, the other is an explanation and at the end you can should find "applies to ... "

it's easy. If your policy applies to windows server 2003 it will be applied to 2008 too. If it's for 2008, the 2003 version just ignores this setting. You can check each policy, there's a section called "apply to" under "explanations"