Jump to content

valter

Member
  • Posts

    427
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Denmark

Everything posted by valter

  1. 1. Q: How to create Roaming User Profiles on Windows Server 2003? A: On your server, create a folder called Profiles and Share it as Profiles$, set share rights as follows: Administrators Full Control Everyone Change Let's say your server name is Server1. Open Active Directory Users and Computers, open your target users container, double click on the User and click tab Profile. In the field Profile Path type the following: \\Server1\Profiles$\%username% Next time the user logs on, his/her profile folder will be automatically created. Now, if you're using Windows Server 2003, open your Group Policy for the domain or just edit the Default Domain Policy (right click on Domain Name in Active Directory Users and Computers, click Properties, click tab Group Policy and then Default Domain Policy or just edit one of your own), navigate to Computer Configuration\Administrative Templates\System\User Profiles and locate policy called Add the Administrators security group to roaming user profiles, then set it to Enabled.
  2. On your server, create a folder called Profiles and Share it as Profiles$, set share rights as follows: Administrators Full Control Everyone Change Let's say your server name is Server1. Open Active Directory Users and Computers, open your target users container, double click on the User and click tab Profile. In the field Profile Path type the following: \\Server1\Profiles$\%username% Next time the user logs on, his/her profile folder will be automatically created. Now, if you're using Windows Server 2003, open your Group Policy for the domain or just edit the Default Domain Policy (right click on Domain Name in Active Directory Users and Computers, click Properties, click tab Group Policy and then Default Domain Policy or just edit one of your own), navigate to Computer Configuration\Administrative Templates\System\User Profiles and locate policy called Add the Administrators security group to roaming user profiles, then set it to Enabled.
  3. I don't think BETA would make much difference from final release anyway ... so you can try to play around with BETA and see what happens
  4. Okay, so if I am configuring arbitrary servers in my domain that are not domain controllers, then I necessarily will not configure domain and domain controller policies for each one..? <{POST_SNAPBACK}> you will configure Default Domain Policy ... anyway, it's not good idea to configure DEFAULT DOMAIN POLICY, but rather make your own and set it to no override ...
  5. 1000 x thanks I do have other firewall, but security policy says Windows firewall MUST be enabled so I need to find the way to open certain ports for Symantec AV (RTV Scan) and other ...
  6. Huh .. I have too many servers anyway lol 2 x DELL PowerEdge 2600 Dual P Xeon @ 2800 MHz 2 GB RAM 440 GB Hard Drive Space (SCSI 10K) LTO Backup Device 200/400 GB Server1 hosting: User home folders and shares and Problem reporting and inventory system Server2 hosting: Finance Applications and Data 3 x COMPAQ Prolian ML 370 G1 Dual P III @ 1000 MHz 1,5 GB RAM 440 GB Hard Drive Space (SCSI 10K) LTO Backup Device 200/400 GB Server1 hosting: IT Applications and Data, Intranet Server2 hosting: PDC Emulator, Domain FISMO roles, DHCP Server3 hosting: nothing Custom Made server Rack 1U P4 @ 2600 MHz (Intel S845WD1-E) 2 GB RAM 300 GB Hard Drive Space (IDE) LTO Backup Device 80 GB Server hosting: GIS Application and Data Company size: 35 people Research company, all data MUST be available at all time. Never saw smaller company with more data lol
  7. I can get you some cheaper tapes if you want ... new of course
  8. I would, but my security strategy requires to use both the internet and windows firewall ...
  9. Default Domain Policy applies to all computers in the domain Default Domain Controller Policy applies only to Domain Controllers in the domain
  10. I was just about to ask you in pervious post how do you access gpo ... anyway, if you use gpedit.msc, you're right, you can't see those policies there ... but if you click on DOmain controller or Domain Policy in Administrative Tools Folder then you will be able to access aforementioned settings ... same if you right click on your domain name in Active Directory Users and Computers - Properties - Group Policy
  11. These are for Win2k3 server standard edition %ALLUSERSPROFILE% Local Returns the location of the All Users Profile. %APPDATA% Local Returns the location where applications store data by default. %CD% Local Returns the current directory string. %CMDCMDLINE% Local Returns the exact command line used to start the current Cmd.exe. %CMDEXTVERSION% System Returns the version number of the current Command Processor Extensions. %COMPUTERNAME% System Returns the name of the computer. %COMSPEC% System Returns the exact path to the command shell executable. %DATE% System Returns the current date. Uses the same format as the date /t command. Generated by Cmd.exe. For more information about the date command, see Date. %ERRORLEVEL% System Returns the error code of the most recently used command. A non zero value usually indicates an error. %HOMEDRIVE% System Returns which local workstation drive letter is connected to the user's home directory. Set based on the value of the home directory. The user's home directory is specified in Local Users and Groups. %HOMEPATH% System Returns the full path of the user's home directory. Set based on the value of the home directory. The user's home directory is specified in Local Users and Groups. %HOMESHARE% System Returns the network path to the user's shared home directory. Set based on the value of the home directory. The user's home directory is specified in Local Users and Groups. %LOGONSERVER% Local Returns the name of the domain controller that validated the current logon session. %NUMBER_OF_PROCESSORS% System Specifies the number of processors installed on the computer. %OS% System Returns the operating system name. Windows 2000 displays the operating system as Windows_NT. %PATH% System Specifies the search path for executable files. %PATHEXT% System Returns a list of the file extensions that the operating system considers to be executable. %PROCESSOR_ARCHITECTURE% System Returns the chip architecture of the processor. Values: x86 x86 Refers to microprocessors that have or emulate the 32-bit Intel processor architecture.or IA64 (Itanium Itanium An Intel microprocessor that uses explicitly parallel instruction set computing and 64-bit memory addressing. Itanium-based refers to systems or platforms that are based on the Itanium processor. Itanium 2-based refers to systems or platforms that are based on the Itanium 2 processor. Itanium architecture-based refers to systems or platforms that are based on the Itanium and Itanium 2 processors. -based). %PROCESSOR_IDENTFIER% System Returns a description of the processor. %PROCESSOR_LEVEL% System Returns the model number of the processor installed on the computer. %PROCESSOR_REVISION% System Returns the revision number of the processor. %PROMPT% Local Returns the command prompt settings for the current interpreter. Generated by Cmd.exe. %RANDOM% System Returns a random decimal number between 0 and 32767. Generated by Cmd.exe. %SYSTEMDRIVE% System Returns the drive containing the Windows server operating system root directory (that is, the system root). %SYSTEMROOT% System Returns the location of the Windows server operating system root directory. %TEMP% and %TMP% System and User Returns the default temporary directories that are used by applications available to users who are currently logged on. Some applications require TEMP and others require TMP. %TIME% System Returns the current time. Uses the same format as the time /t command. Generated by Cmd.exe. For more information about the time command, see Time. %USERDOMAIN% Local Returns the name of the domain that contains the user's account. %USERNAME% Local Returns the name of the user who is currently logged on. %USERPROFILE% Local Returns the location of the profile for the current user. %WINDIR% System Returns the location of the operating system directory.
  12. Sure m8, create a folder called Profiles and share it as Profiles$, then on each user account properties sheet, profiles tab, Profile field type in something like this \\servername\Profiles\%username% next time user logs on, their profile folder will be automaticaly created ... note that My Documents folder is part of a user profile, so if they have too many files, it will take ages to copy everything over to the server, as well as every time they log on ... as per user home folders ... create a folder calles Users, and create each user folder calles after their username, set sharing and security permissions and then add this in your logon script ' Mapping user home folder on the server Dim oNet, sUser Set oNet = CreateObject("Wscript.Network") sUser =oNet.UserName oNet.MapNetworkDrive "P:", "\\SERVER\" & sUser Note P:\ is the letter of the drive you want to map .... \\SERVER\ needs to be changed to your server name ... if you don't have logon script ... here is a simple one ... ' VBScript. ' Mapping user home folder on the server Dim oNet, sUser Set oNet = CreateObject("Wscript.Network") sUser =oNet.UserName oNet.MapNetworkDrive "P:", "\\SERVER\" & sUser ' Mapping user network drivers on the server Dim WshNetwork Set WshNetwork = WScript.CreateObject("WScript.Network") WshNetwork.MapNetworkDrive "Q:", "\\SERVER\Public Folder" WshNetwork.MapNetworkDrive "R:", "\\SERVER\IT" WshNetwork.MapNetworkDrive "S:", "\\SERVER\Share" ' Mapping user printers from the server Dim net Set net = CreateObject("WScript.Network") net.AddWindowsPrinterConnection "\\SERVER\HPLJ8100", "HPLJ8100" net.AddWindowsPrinterConnection "\\SERVER\TOSHIBA e-STUDIO 211c", "TOSHIBA e-STUDIO 211c" net.AddWindowsPrinterConnection "\\SERVER\TOSHIBA e-STUDIO200", "TOSHIBA e-STUDIO200" Set net = CreateObject("WScript.Network") net.SetDefaultPrinter "\\SERVER\HPLJ8100" Save it as whatver.vbs and place it inside NETLOGON folder Hope this helps
  13. I don't think there is logical explanation to the problem you experience ... anyway, you can try to reinstall AD, or try to recreate default policy using the attached tool. Please note that you will run this tool on your own responsibility recreateDefPol.zip
  14. Anyone knows how to control windows forewall ports through Active Directory? I want to open certain ports on all workstations ... any help is appreciated ..
  15. For crying out loud quit your "wannabe" ramblings, I'm bored with your banal comments! <{POST_SNAPBACK}> Is this the best you've came up with? Lame and poor, dude, lame and poor ...
  16. If you don't have MSI, or don't know how to make a MSI file, you can distribute it using ZAP files ... search on MS Support for article how to distribute software using ZAP files
  17. You can give them read rights on parent filder and write rights on the folder you want ...
  18. How is this done? thx <{POST_SNAPBACK}> just install gpmc on the server and run it from there ... once in gpmc, expand forest, then domain, click on Group Policy Object, then right click on Default Domain Policy and then Back up ...
  19. Well I've used SI 0680 Win2k drivers on Win2k3 Standard Edition and had no problems ... anyway, try this attached driver EDIT: couldn't attach driver 3+ MB ... try from here ... http://members.driverguide.com/driver/deta...driverid=332154
  20. well maybe you should take your sick ego a bit down ... when you lears basics of a culture then you can talk to me, until then, take that competence of your and stick it right up your arse ... you might just feel better
  21. I remember reading some posts from people that have same problem, and one solution was to run gpmc on the server and then try to backup gpo
  22. Well if you don't mind I would leave judgment of my knowledge to more competent people than you are ...
  23. The way you call your internal AD domain has nothing really to do with the Internet domain .. but it's painless if you call your internal domains xxxx.local rather than xxxx.com (.local is the keyword) anyway your problem might be the following: 1. GPO, because Eddie is not member of any group that can access the server. Try to create new GPO on the OU where Eddie is located, edit GPO, find settings "Access this computer from the network" and add the group Eddie is member in. 2. Your server has 2 NIC (network interface card) and you have problem with replication (browser errors in Event Log) Please post some more details about your Event log so we can help you ... it isn't something difficult, so no worry ...
×
×
  • Create New...