Windows 10: OSD - Incrementing Computer Names for shared NIC / Docking

Hi,

I have been given permission from Johan Arwidmark to post this. Some of his MDT Database extensions are used and modified to create this solution.

Most of today's new laptop devices does not have a RJ45 NIC, only Wi-Fi is included. To support OSD over PXE, you need to use a USB NIC or USB docking, making the MAC address shared by multiple computers. For PXE identification, excluding the MAC address is easily accomplishable.

However, if you use the MDT database for assigning incrementing OSDComputername, there are some modifications needed. For unique MAC addresses, Johan Arwidmark has provided a great solution for this. To support shared MAC Addresses, I have modified this solution to identify or create OSDComputername with UUID as the identifier. If computers are in the MDT database with MAC address and UUID is null, the row is updated with the UUID of the Computer.

I have provided 2 files to hopefully be able to help others. One contains a script to create the "IdentifyComputer_UUID" Stored Procedure. The other one is a CUSTOMSETTINGS.INI file where CSETTINGS is only using UUID for the query.

:)

 

Sync as new device everytime

yes. both devices have totally different ID.



the scenario.



1. First device sync (device ID: Nic)

- create partnership & sync files. OK



2. Undock Nic



3. Second device sync (device ID: Mat)

- create partnership & sync files. OK



4. Undock Mat



5. Dock Nic & the activesync ask to create new partnership while this step have been done in step no. 1.

- create new partnership of which whether delete / rename / remain the same name (all 3 options tried) & sync file. OK



6. Undock Nic



7. Dock Mat & still, activesync ask to create new partnership while this step have been done in step no. 3.



it happens everytime i'm docking the device every single attemp to sync.



Please help & thanks for the reply.

 

Name resolution oftentimes stops working -- until I re-install the network adapter

The name resolution problem happened again this morning; I could access the other PC by IP address but not by computer name. To clarify: I could see the shares on the other PC if I used its IP address but could not access the other PC by its name; attempting
to do so produced the following error:

Windows cannot access \\PC05

Error code: 0x80070035

The network path was not found

NetBScanner displays PC05, with the IP address.

I figured I would try a trace route to the IP address of the other PC. It found the PC immediately, but with the computer name of PC05.lan -- note the ".lan" suffix! What's that all about?

After I uninstalled/re-installed the NIC, I could access PC05 (including its shares) by computer name again.

BTW, when I browse to \\PC05.lan (either before or after uninstalling/re-installing the NIC), I'm prompted for credentials.

 

This information has already been known about for sometime. Do not know who this OP is, nor why they would tell someone something that has been out on Microsoft's Technet for years.

 

I am sure others in the Community has found a way to solve the same issue. I worked out this solution, and enjoy sharing it with others. There's a lot of amazing people in the Community that shares knowledge, and they're a big part of making me who I am professionally.