Problem regarding imaging and netbios name


Recommended Posts

hello gang,

i have a new problem which seems to have stumped me. I recently updated an already created image (Ghost), created a new image of that system then rolled it out to approx 30 client computers. the procedure i use is this:

1 Install O/S and apps

2 Configure (using a specifically created admin account) profile to copy to default user

3 run sysprep (with the option left on to regenerate sids)

4 and whilst the computer is DOWN (as in before it boots to create new sids and follow my sysprep.inf answer file) i ghost that image.

So theorectically i can rollout fresh images that havent finshed initializing or joined domains yet, to ensure these are REALLY individual images. sysprep then continues and domain attachment is automated via sysprep.inf so i end up with computers ready to rock and roll.

My problem now stems from the fact that on my LAST set of images, the netbios name seems to have been copied across to every image. Now this is peculiar as when i look at each computer in the my computer properties, computer name, more, netbios name, it actually says the computer unique name. As expected ofcourse. But when i ping a recently imaged computer from another computer with the command "ping -a NEWIMAGE1" i recieve a reply from the correct ip adress, but of the netbios name of the host image computer before sysprep was run on it.

Let me say that bit again, the host image (the computer my image was created from) had a computer name of 'Image010306Builda', and such a netbios name of the same up 2 15 characters ofcourse. Sysprep was run on this computer to regerate sids and the like. When this computer shutdown after sysprep i imaged it. My new images all got new computer names (during the sysprep procedure). But now when i interogate these computers they have the same netbios name as the originaal host computer, whilst their own netbios name configuration IS their own (correct) dns computer name.

i cant seem to find the cause of this. I had a WINs server in operation but removed it for clarity sake, it did not have any records regarding my issue anyway.

Any help please, especially from S.O.E admins or anyone really. Thanks alot guys.

Hi amfony,

This may sound strange but we had exactly the same issue at our DR site recently.

You'll find all the machines are pinging via WINS instead of DNS i.e. WKS001 instead of WKS001.domain.co.uk)

Anyway, the fix the engineering team implemented was to script in an "ipconfig /release" and "ipconfig /release" upon the final boot (after our image was rolled and had at least once booted into windows).

Try that on one machine and then try pinging...you should be able to via DNS and resolve name correctly.

What I couldn't understand was a reboot was NOT resolving the issue...it required a forced ipconfig release and renew. Very strange indeed.

Please post an update here whatever the outcome.

Many thanks

i tried but no dice. under every circumstance i get the same reply. i even ran sysprep again on a image client machine, removed ut from domain, uninstalled the nic, rebooted, searched registry, i disabled netbios expliocilty from the nic, (its disabled by dhcp by default) and no dice. i am at a loss

Where are you resolving these names from? Your machine? Every other machine on the network? Where?

Sounds like you have a cached entry or lmhost/host entry in where ever your trying to access these machines from.. What does a nbtstat -A IPADDRESS of the machine in question show?

What does your cache show on the machine your doing these queries from? nbtstat -c

What does the machine in question show for nbtstat -n show?

Sorry for the late reply guys! but i am back now

Sorry budman i should have been more specific, from the newly created image (lets name it CLTIMG) when i ping it self, i get returned its proper "dns" fqdn (and proper address), when i type the command "ping -a IPADDRESS OF SELF" i get the CORRECT DNS name relpy again. Now this is what i expect as i have disabled netbios via DHCP options.

When i ping from ANOTHER (any other) computer to the CLTIMG via its proper name, i get a correct and legitmate dns response (my ddns is working fine and all records are correct for the new images), from anyother computer when i type "ping -a IPADDRESSOFCLTIMG" i get resolved back "ORIGINALIMG" (being the image i copied to rollout to client machines) and the ip address of the CLTIMG box.

Sorry if i am not very clear, but when resolving from it self, the CLTIMG thinks everything is ok. When resolving netbios from another computer it gives me the wrong computername.

I did go through pretty much nbtstat had to aoffer me budman and to confuse me even further when i typed "nbtstat -a CLTIMGIPADDRESS" i get the CORRECT netbios name returned to me.

in the cache if the CLTIMG i get nothing the domain name (which is wierd as i shudnt have any entries here is my netbios is disabled) and nbtstat -n gives me once again my correct computer name.

Interesting no?

I am thinkning along the lines that sysprep itself didnt quite work as supposed to rather then any configuration errors. What is your line of thniking budman? and others ofcourse?

Thanks guys and sorry again about the late reply

I've built plenty of machines and joined them to a domain for tweaking before ghosting, BUT I always remove them from the domain and remove the comp account in AD prior to actually making the image. I havent seen any odd issues form doing so and usually use sysprep to have them prompt for a new name prior to joining the domain on first boot after applying the image...

The problem as it sounds to me is more of a DNS issue than a workstation issue... Maybe try removing the DNS entry for the particular machine that your pinging then renew the IP of that machine and have a new DNS record created. Then of course ping it from somethign else... OR, maybe remove the problem machine from the domain, remove the comp account in AD, rename it and rejoin the domain... Either of these will basically allow DHCP to update DNS with a new record for that machine, and hopefully resolve your problem.

ok that could be the problem, the fact that i DONT remove the computer from the domain b4 sysprep-ing. I was under the assumption that a reseal on sysprep was the equivalent of "making the system ready to be used by end users", and therefore assumed all naming and domain membership was revoke and nullified before sysprep was finshed its job. As well as re-sid-ing.

Now ill have to test this tomorrow, but just a thought. I too, have built plenty of computers, it seems in error with my mistake regarding the domain. But i have now in a prodcution environemnt 95% of my images running well. As in NOT WITH THIS PROBLEM. i dont feel that my procedure this time was any different from the other systems i have built then imaged.

I called micro$oft, with a capital SOFT, and i explained my issue, as soon as i mentioned "3rd party deployment application" they washed theirs hands of the problem and said "we cant guarentee anything with 3rd party products".

As for UnaBonger, the records i have delted and to no avail, the first post actually refers to new ip lease and that was no dice either.

Im back wit the results, I did create a new image with removing the domain, this didnt seem to fix it.

I have recoursed back to creating a brand new installation of XP from my custom install CD. Customised, removed from domain as suggested in this thread and imaged. This works.

Unfortunatley i cannot pin point the problem, but a work around will do until i get more time to investigate. Thanks for all your help guys with this issue.

Sincerley

Amfony

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Windows 11 KB5060826 optional update brings better Setup, new data migration tool, more by Sayan Sen Alongside KB5060829 for Windows 11 24H2, Microsoft has also released its C-release non-security preview update for Windows 11 23H2 and 22H2 today. The new update is rolling out under KB5060826 (builds 22621.5549 and 22631.5549). KB5060826 brings an upgraded Setup which will now let admins choose whether to deploy critical updates during the OOBE (the initial out-of-box experience setup on Windows). Alongside that, it also adds the new PC migration experience on Windows Backup, as well as the default app changes related to the European Economic Area (EEA) region. The full changelog is given below: First up we have the changes and improvements for Gradual Rollout: [App defaults] New! We are rolling out some small changes in the European Economic Area (EEA) region for default browsers through the Set default button in Settings > Apps > Default apps: Additional file and link types will be set for the new default browser, if it registers them. The new default browser will be pinned to the Taskbar and Start menu unless you choose not to pin it by clearing the checkboxes. There is now a separate one-click button for browsers to change your .pdf default, if the browser registers for the .pdf file type. [PC Migration] New! The PC-to-PC migration experience in Windows is starting to roll out. You’ll begin to see the landing and the pairing page in the Windows Backup app, giving you a first look at what’s coming. In the full experience, you’ll be able to transfer files and settings from an old PC to a new one during setup. Support for this feature during PC setup will arrive in a future update. The rollout is being introduced in phases to support a smooth experience. [Windows Share] ​​​​​​​New! When you share links or web content using the Windows share window, you will see a visual preview for that content. Up next, we have Normal Rollout features: [Windows Setup] New! Admins can configure whether a new device gets critical updates during the out-of-box experience (OOBE). The update has a single known issue related to Noto fonts. You can view the support article here on Microsoft's official website. The update can be obtained by clicking on "Check for optional updates" inside Windows Update. You can also download it manually from Microsoft Update Catalog website.
    • American? Yer whole 120v limitation is madness.  You can still get low powered pcs , nice, that'll do the job 
    • People want a resizable taskbar, not tiny icons on a fat one. Microsoft, you've done it again.
    • Windows 11 gets resizable taskbar icons, PC Migration tool, and more in KB5060829 by Taras Buria Windows 11 24H2 users, it is time for this month's non-security update. KB5060829 is here, and it has some long-requested taskbar updates, a new tool for transferring files between PCs, and a hefty list of other improvements. With KB5060829, build number 26100.4484, Microsoft is finally delivering the long-requested small taskbar icons, one of the missing Windows 10 taskbar features. However, with Windows 11, Microsoft gives users more flexibility: you can have your taskbar as is, make icons smaller as the taskbar gets full, or keep icons small all the time. Neat! Additionally, a new PC Migration app is available, which enables transferring files from one PC to another during the initial setup. However, in a somewhat confusing move, all users receive only the landing page and the pairing page. The actual capability is coming in a future update. Other changes include performance improvements in File Explorer for handling large archives, fixes for display flashing, new accessibility features, and more. Here is the complete changelog (gradual rollout): [App defaults] New! We are rolling out some small changes in the European Economic Area (EEA) region for default browsers through the Set default button in Settings > Apps > Default apps: Additional file and link types will be set for the new default browser, if it registers them. The new default browser will be pinned to the Taskbar and Start menu unless you choose not to pin it by clearing the checkboxes. There is now a separate one-click button for browsers to change your .pdf default, if the browser registers for the .pdf file type. [Click to Do (Preview)] New! Ask Microsoft 365 Copilot is a new action in Click to Do on Copilot+ PCs. Use it to send text or images to Microsoft 365 Copilot, which will respond to your questions. The Ask Microsoft 365 Copilot action requires a Microsoft 365 license and follows your organization’s privacy policies. [Narrator] New! The Screen Curtain feature in Narrator helps protect your privacy and improve focus by blacking out the screen while Narrator reads content aloud. This is especially helpful in public or shared spaces, where you can work with sensitive information without others seeing your screen. To turn on Narrator, press Ctrl + Windows + Enter. Then press Caps Lock + Ctrl + C to turn on Screen Curtain. While it’s on, you can use Narrator as usual with the screen hidden. Press Caps Lock + Ctrl + C again to turn it off. New! Narrator makes it easier to discover and learn about its features directly within the experience. Whether you're new or exploring advanced options, Narrator will guide you through the latest updates using a series of steps and prompts that explain each new feature and change. [PC Migration] New! The PC-to-PC migration experience in Windows is starting to roll out. You’ll begin to see the landing and the pairing page in the Windows Backup app, giving you a first look at what’s coming. In the full experience, you’ll be able to transfer files and settings from an old PC to a new one during setup. Support for this feature during PC setup will arrive in a future update. The rollout is being introduced in phases to support a smooth experience. [Settings] New!​​​​​​​ The Settings homepage managed by IT admins now includes cards tailored for enterprise use. These include familiar options like "Recommended settings" and "Bluetooth devices" along with other new cards for device info and accessibility preferences. If a user signs in with both a work or school account and Microsoft account, an additional account card appears to show both account types. New! The country or region selected during device setup now appears under Settings > Time & language > Language & region. Fixed: The storage card in Settings > System > About shows an incorrect or unreadable character instead of the proper disk size. [Taskbar & System Tray] New!​​​​​​​ ​​​​​​​​​​​​​​The taskbar now resizes icons to fit more apps when space runs low, keeping everything visible and easy to access. You can adjust how icons appear in settings—reduce icon size only when the taskbar is full (default), keep icons at their original size at all times by selecting Never, or use smaller icons all the time by selecting Always. To change this setting, right-click an empty area on the taskbar, select Taskbar settings, expand the Taskbar behaviors section, and choose your preference under Show smaller taskbar buttons. New! In addition to the new grouping of the Accessibility menu in Quick settings, there are text descriptions for the assistive technologies like Narrator, Voice access, and more for easier identification and learning. New! Adjusted the indicator (pill) under taskbar apps to make it wider and more visible.​​​​​​​ Fixed: WIN + CTRL + Number doesn't work anymore for switching windows of an open app in the taskbar.​​​​​​​ Fixed: When using taskbar in Windows, the media controls that appear in the preview windows for apps might unexpectedly flicker. [Voice Access] New! You can now use Voice access to navigate, dictate, and interact with Windows using voice commands in Simplified Chinese, Traditional Chinese, and Japanese. New! You can add custom words to the dictionary in voice access. The feature will be available in all the currently supported voice access languages. [Windows Share] ​​​​​​​New! When you share links or web content using the Windows share window, you'll see a visual preview for that content. New! In the Windows share window, you can select a compression level—High, Medium, or Low Quality—when editing and sharing images, instead of selecting from a 0–100 scale. [Color] Improved: Adjusted the location of the intensity and color boost sliders under Settings > Accessibility > Color Filters, so the color previews at the top of the page remain visible while adjusting the sliders. [File Explorer] Improved: Performance has been enhanced when extracting archive files - this will particularly help in the case of copy pasting large numbers of files out of large 7z or .rar archives. [Graphics] Improved: Made underlying changes to enhance display related user experiences, including reducing screen flashing during certain display configuration transitions and eliminating unnecessary display resets that occurred in some cases​​​​​​​. Fixed: Some displays might be unexpectedly green. Fixed: If User Account Control (UAC) is set to Always Notify and the button under Settings > System > Display color calibration is selected for your display and canceled, Settings will stop responding. [Input] Fixed: Typing in Japanese with the touch keyboard might stop working after switching to typing with an English keyboard and then switching back. [MSFTEdit.dll] Fixed: Some apps like Sticky Notes and dxdiag might stop responding when the display language is set to Arabic or Hebrew display. [Quick Settings] Fixed: The top three buttons in the top row don’t respond when selecting to enable or disable them. [Printing] Fixed: Printed lines might be unexpectedly thicker than expected. [Scripting] Fixed: Running a script on a remote Server Message Block (SMB) share might take an unexpectedly long time if the share is hosted on an older Windows Server version like Windows Server 2019. [Windowing] ​​​​​​​Fixed: When you press ALT + Tab to switch out of a full screen game, other windows like Windows Terminal might stop responding. Fixed: An underlying issue might lead to unexpected changes to window size and position after sleep and resume on some devices. Fixed: Explorer.exe might stop working unexpectedly when a window is dragged, if window snapping is enabled. And here is what is available to all users right away: [Copilot] Fixed: Improved the Copilot key’s reliability and resolved an issue that prevented users from restarting Copilot after using the key. [Performance] Fixed: This update addresses an issue to maintain efficiency of Storage Spaces Direct (S2D). When running complex software defined data center (SDDC) related workflows, it’s possible the system might become unresponsive. [Storage optimization] Fixed: An issue that prevented unused language packs and Feature on Demand packages from being fully removed, which led to unnecessary storage use and longer Windows Update installation times. [Windows Hello] Fixed: This update addresses an issue that prevented the automatic renewal of expiring certificates in Windows Hello for Business. [Windows Search] ​​​​​​​Fixed: Windows Search responds very slowly—Search can take over 10 seconds to load before you can use it. Fixed: This update enhances the reliability of Windows Search and resolves an issue that prevented users from typing in Windows Search in some cases. Known issues remain the same: there is a bug where Windows 11 renders Noto fonts poorly in Chromium-based browsers when the display scaling is set to 100%. A temporary workaround is to set the scaling to 125% or higher. You can download KB5060829 by heading to Settings > Windows Update. Alternatively, get it from the Microsoft Update Catalog using this link.
    • 4TB 2TB WD_BLACK SN8100 Gen5 NVMe 2280 SSDs are nice deals for sure by Sayan Sen Storage comes in different forms, both fast and slow, large and small. For example, the Seagate Exos 20TB and BarraCuda 16 TB are high-capacity CMR hard disk drives, and they are currently still selling at great prices. On the other hand, we have SSDs, which are much faster. The SK hynix P41 Platinum, for example, is a PCIe 4.0 drive and it is up for grabs at $120. If you need something faster, then take a look at Western Digital (WD) options, wherein we have the SN8100 PCIe Gen5 NVMe SSD at the lowest prices of just $480 for the 4TB variant and $260 for the 2TB variant (purchase links down below). Since this is a PCIe 5.0 SSD it is very fast, but like other Gen5 drives, it gets very hot especially for sustained reads and writes. So a heatsink is definitely recommended. The S8100 promises sequential reads of up to 14900 MB/s and sequential writes of up to 14,000 MB/s. In terms of random reads, it is rated for 2.3 million IOPS (input output operations per second) and random writes of up to 2.4 million IOPS. There are two reasons for the high random throughputs, first is the DRAM, as the SN8100 packs its own DRAM cache instead of relying on system memory, and second, the relatively new NAND technology called CMOS directly bonded to array (CBA) that helps boost interface speed. Speaking of NAND, the SN8100 features TLC, or triple-level, cells which provides excellent endurance and this 4TB drive is rated for 2400 TBW, while the 2TB is at 1200 TBW. Get the WD SN8100 at the links below: WD_BLACK 4TB SN8100 - WDS400T1X0M: $479.99 (Sold and Shipped by Amazon US) || $479.99 (Sold and Shipped by Newegg US) WD_BLACK 2TB SN8100 - WDS400T1X0M: $259.99 (Sold and Shipped by Amazon US) || $259.99 (Sold and Shipped by Newegg US) This Amazon deal is US-specific and not available in other regions unless specified. If you don't like it or want to look at more options, check out the Amazon US deals page here. Get Prime (SNAP), Prime Video, Audible Plus or Kindle / Music Unlimited. Free for 30 days. As an Amazon Associate, we earn from qualifying purchases.
  • Recent Achievements

    • One Month Later
      jfam earned a badge
      One Month Later
    • First Post
      TheRingmaster earned a badge
      First Post
    • Conversation Starter
      Kavin25 earned a badge
      Conversation Starter
    • One Month Later
      Leonard grant earned a badge
      One Month Later
    • Week One Done
      pcdoctorsnet earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      562
    2. 2
      ATLien_0
      188
    3. 3
      +FloatingFatMan
      175
    4. 4
      Michael Scrip
      144
    5. 5
      Xenon
      115
  • Tell a friend

    Love Neowin? Tell a friend!