Jump to content

BlkCrowe

Member
  • Posts

    15
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About BlkCrowe

BlkCrowe's Achievements

0

Reputation

  1. Thanks for the update. I'll store that tidbit for when I deploy WDS in our environment. Glad you got it working.
  2. Just checking. Sorry I cant help beyond the ESX clone/migration as I have not used WDS at all. Hopefully another Admin will step in. Good luck.
  3. Did you use VMWare Converter or just use an imaging tool to to clone the physical server?
  4. I've been wanting to try FREENAS for a while, but never got around to it. Since I really just want a place to store my data and share it with the wife's computer and both kids' computers, FREENAS may work just as well...or even better. It has a much smaller footprint and can darn near run on a x486 computer! But, being a Windows Administrator (in the "Real World"), I decided to give WHS a shot since I realize that Microsoft butters my bread. :-)
  5. I have the 2 drives connected to a Promise Fasttrak TX2 PCI card. I created the mirror set on the PCI card and not using Windows. I did this before I even installed WHS, not knowing how the file system was handled. I had heard you could create duplicate folders and such, but if I was going to put all my data on one system, I wanted to insure that I had a second copy. I'll probably change it on the next install so that I have 400GB of disk.
  6. That is by design due to the nature of the "file system" in WHS. It still uses NTFS, but it is indexed differently. All disks added will be reformatted when they are added to your disk pool. Be careful!
  7. Have had it installed only a few days and haven't had much time to play with it. From what I have seen so far, it is very promising. This is probably the first OS from Microsoft that I am truly excited about. It is about time that Microsoft recognized that there is a need for this product among "consumers" (as opposed to enterprise/business users). Plan on adding some serious disk to your WHS as your backups will eat up space if you go with the default backups. I've got a 40GB for my OS and 2 x 200GB (RAID 1) for my data in my WHS. I think I am going to add another 200GB RAID set as my music alone is about 120GB. My overall impression: - The installation was easy and I like how it installed all updates during the install - The WHS components are intuitive and the settings are relevant - It appears to be easy enough for the typical home user to get up and running, but have enough features left in it for the more technical users I'm going to put the WHS client piece on my wife's computer tonight to see how well the backup works across a typical wireless home network setup.
  8. This should give you the results you want... for /D /R "%USERPROFILE%\Desktop" %%a IN ( * ) DO echo %%~na Run FOR /? for a list of all the variable substitutions.
  9. Virtualization? Heck yes! I have VMWare ESX 2.53 on 2 x HP 585 Quad-Opteron servers with 32GB RAM and am running 80 VMs between these 2 servers and neither one of them has hit 50% CPU utilization (with all 80 VMs powered up). With Virtual Center, I can "V-Motion" VMs between the 2 servers without ever taking the VM off-line. I'm getting ready to add a 3rd server to my farm and should easily get 120-150 VMs on these servers. I can't wait to get ESX 3.0 installed so that I can take advantage of some of the new High Availabilty and Resource Management features. As for the workstation, I use both VMWare Workstation and Microsoft Virtual PC. While VMWare is by far more powerful than Virtual PC, I usually only neeed the basic functionality that Virtual PC provides. I'm not virtualizing Active Directory or client server applications, so I don't want the overhead that comes with VMWare. In my experience Virtual PC has a smaller footprint and is easier to use for most inexperienced virtual software users. Let me use an "SAT Test" example to describe the 3... Microsoft Virtual PC is to VMWare Workstation as Notepad is to Wordpad VMWare Workstation is to VMWare ESX Server as Wordpad is to Microsoft Word Or for you *NIX guys out there...as Wordpad is to Vi. :-)
  10. There is not a variable for the IP Address out of the box. You can see all the variables from a command prompt by typing SET. I suppose you could add a computer startup script (in a GPO?) to automatically set a variable on each boot. Just remembered this utility: http://www.jsifaq.com/SF/Tips/Tip.aspx?id=4445 You could use it from the startup script by calling: for /f "Tokens=*" %%i in ('techops /ip') do set IP=%%i Of course there is always VBScript. Or any scripting language of your choice.
  11. You could create a forward lookup zone or stub zone in each Domain's DNS to point to the other Domain. This will allow both domains to resolve each other properly.
  12. I don't know of anything more comprehensive than nLite. While I don't use it in my day-to-day professsional environment (we use end-to-end scripted installs), there is certainly no reason that it would not meet "professional" standards. Now I agree that there is a slight learning curve to it (which includes a little trial and error) to acheive the desired results on your hardware platform, but it is worth it. There is nothing that compares or even comes close to what nLite can do...I believe this would be the reply you will get from most users in this forum.
  13. Create a domain group called something like "Local Admins". Open the GPMC and create a new GPO (or edit an existing GPO). Navigate to Computer Configuration/Windows Settings/Security/Restricted Groups Right Click. Select "Add Group..." For Group Name, type "Administrators" and click "OK". Add the following members to this Restricted Group: DOMAIN\Domain Admins DOMAIN\Local Admins Click OK. Link the GPO to the appropriate OU. Close the GPMC. Tell your boss it will take 2 days to complete, then go back to playing Solitaire.
  14. Try this simple batch file: @ECHO OFF ::=== INITIALIZE VARIABLES=== SET SOURCEPATH=C:\DATA SET DESTPATH=C:\CSVFILES ::=== COPY FILES FROM SUBDIRECTORIES === FOR /D %%i in (%SOURCEPATH%\*) DO ( COPY %%i\*.CSV %DESTPATH% ) ::=== OPTIONAL - DELETE ORIGINAL FILES === ::DEL /f /s /q %SOURCEPATH%\*.CSV ::=== ALL DONE === EXIT
  15. There is a known issue in Windows 2003 Server in which shutdown.exe will not properly shutdown a system from a batch file if the system has been accessed via an RDP connection since its last reboot. Microsoft states that you cannot shut it down remotely, be we found we could not even use shutdown.exe in a scheduled script. The exact behavior that we saw, and that documented by Microsoft vary slightly, but the fix resolved our problems. It wouldnt surprise me if this issue exists in Windows XP as well, but hasn't been identified or fixed. http://support.microsoft.com/default.aspx?...kb;en-us;834100 The hotfix for Windows 2003 Server cannot be directly downloaded from Microsoft, but can be requested via email. We have slipstreamed this hotfix into our automated build. Unfortunately, this patch replaces winlogon.exe, so it won;t work with Windows XP.
×
×
  • Create New...