Netman66

Member
  • Content count

    70
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Netman66

Contact Methods

  • Website URL
    http://
  1. The WINS tab gives you the option of enabling LMHOSTS lookup in addition to NetBIOS over TCP/IP either using DHCP or directly. The client will first check it's cache, then WINS, then Broadcast, then the LMHOSTS/HOSTS, then DNS. I've never heard of NetBIOS on TCP/IP, I'm not even sure that's real. The mechanism in Windows is NetBIOS over TCP/IP. The security risk for NetBIOS being enabled is minimal while inside your protected LAN, but the concern is when it's unprotected. NetBIOS forces the computer to advertise it's name and any resources to the network. It also opens ports 137, 138 and 139.
  2. You don't have to have NetBIOS enabled in XP and higher OSes - IF - you have alternate methods of resolution available (LMHOSTS, WINS or DNS). In XP, NetBIOS is used primarily for the Browser Service to allow you to "see" other computers on your subnet and in the same workgroup or domain. Without this enabled, the computer cannot use any broadcast method to discover what's around them and must rely solely on other resolution methods. This is significant when you are trying to share folders from each machine so they are accessible to other workstations on the network. Theoretically, you can shut down NetBIOS over TCP/IP and still function - and to a point it will, but you'll need to either use an LMHOSTS file or WINS oe local DNS server with WINS integration enabled to be able to browse shares or connect using UNC names rather than IP addresses. For a local network such as yours and as long as you have a firewall between you and the internet that is correctly configured then leaving NetBIOS enabled is likely the way to go. Hope this helps.
  3. Just search for all .CPL files. Remove the nVidia one. If you're still unhappy with that, then in the registry here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Search for the nVidia stuff Delete the entire key and branch for the nVidia drivers.
  4. If it was done via registry entry it is likely here: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Winlogon DefaultUserName "Administrator" DefaultPassword "{your password}" AutoAdminLogon "1"
  5. Glad you're up and running, but there were links in that document I posted explaining how to change your network to something different - this may have saved you some time.
  6. You may also want to read through this and see if anything there is not configured properly on 7. http://www.vistax64.com/tutorials/126910-s...ing-enable.html
  7. I see that the username box contains the PC name prefix. Try changing this to the servername\username.
  8. Download and install this: http://downloadcenter.intel.com/T8Clearanc...ws〈=eng This should install and update your drivers and software.
  9. It almost sounds like you have a non-AHCI image and the BIOS on the targets have the SATA mode set to Native. See if setting it to combo or compatible solves it. Let us know.
  10. We have hundreds of D610s and they all PXE boot after turning it on in the BIOS.
  11. Yes. No problem at all.
  12. Is there any reason you aren't simply using the [CPU] section instead? We started down the Model path, but realized the utility has the capability to figure out whether it's MP or UP and the Vendor (AMD or Intel) - so we let the utility do the work for us. Simply un-remark the 4 lines under [CPU] and be sure the other sections are remarked out again.
  13. You may have some luck using something from this article: http://www.rtfm-ed.co.uk/?page_id=174 You want a P2V tool to create your Virtual Machine from the Physical one.
  14. The $OEM$ folder sits at the same level as i386. The fault lies in the SIF the way I see it. MsDosInitiated="0" should actually be MsDosInitiated=No UnattendedInstall="Yes" should be UnattendedInstall=Yes Depending on whether you want to be prompted for the installation partition the value of AutoPartition set to 0 will prompt, 1 will not.
  15. Dude....edit out your product key.... As for why your script doesn't work - your path is wrong. Your OEM structure is like so: $OEM$>$1>APPLICATIONS Which would mean the Applications folder would be copied to the root of C drive. Your script is calling this path: %systemdrive%\install\Applications\net2\netfx.msi /qb ADDEPLOY=1 ...which would imply everything is installed to C:\Install\Applications. Either fix the OEM stucture or fix the script to remove \Install.