How to get DP name via script

Question

Hello,
We are migrating from Symantec Altiris to SCCM 2012. In our current environment we have both HP models and now moving towards Lenovo models. We are using both respective Enterprise solutions for managing driver that is HP SSM and Lenovo Thininstaller.
We have 3 sites/locations with exactly the same shares on each one. We are using a script with a built in Altiris token that finds out what DP or Taskserver (in Altiris Environment) the client is connected to.
How can I define a DP with the same type of script in SCCM?
Are there any tokens for DP?
Are there any specific local files or usuble values that changes when connecting to other DPs?
Can I somehow query bounderies in a script and then use IF statement to connect them to a specific share?
I know that I can use one share if I want to but that will use a lot of network trafic since we have the DPs on different locations throughout the country. One idea I had was to make 3 different packages with one DP specified in each
one and then connect them to its specific boundary.  
The good part to make it work all in one script is that it can be applied to any client in the organisation to update their current drivers and not just to use in initial deployment.
I found a vbs script that can echo a DP, but how do I implement it into my script?
http://sccmguru.wordpress.com/2014/04/22/show-dp-in-use-during-task-sequence/
'// Purpose: Used to find active Distribution Point
'// Version: 1.0 - April 15, 2014 - Odd-Magne Kristoffersen
'// This script is provided "AS IS" with no warranties
Set env = CreateObject("Microsoft.SMS.TSEnvironment")
ENV_SMSTSHTTPTHI0000D = env("_SMSTSHTTPTHI0000D")
SMSTSHTTPTHI0000D = Split(ENV_SMSTSHTTPTHI0000D,"/",-1,1)
DP = split(SMSTSHTTPTHI0000D(2),".",-1,1)
Echo DP(0)  
Here is my script in short format. I didn't bother putting all the models.
The value %MODEL% is from the Query in the beginning of the script and the %TASKSERVER% value is an Altiris token the can be used when running a script with the agent credentials.
@echo off
set model=
FOR /F "tokens=2 delims='='" %%A in ('wmic ComputerSystem Get Model /value') do SET model=%%A
Echo This is a %MODEL%
IF "%MODEL%" == "HP EliteBook 820 G1" GOTO HP Updates
IF "%MODEL%" == "HP EliteBook 840 G1" GOTO HP Updates
IF "%MODEL%" == "HP Compaq 8000 Elite SFF PC" GOTO HP Updates
IF "%MODEL%" == "HP Compaq 8100 Elite SFF PC" GOTO HP Updates
IF "%MODEL%" == "HP Compaq 8200 Elite SFF PC" GOTO HP Updates
IF "%MODEL%" == "HP Compaq Elite 8300 SFF" GOTO HP Updates
IF "%MODEL%" == "20AQ007UMS" GOTO Lenovo Updates
IF "%MODEL%" == "20AL00BYMS" GOTO Lenovo Updates
IF "%MODEL%" == "10AB000YMX" GOTO Lenovo Updates
IF "%MODEL%" == "20C0003TMS" GOTO Lenovo Updates
IF "%MODEL%" == "20AL007NMS" GOTO Lenovo Updates
IF "%MODEL%" == "10AAS0HN00" GOTO Lenovo Updates
exit 1
:Hp Updates
\\%TASKSERVER%\Share\ssm.exe \\%TASKSERVER%\Share /ACCEPT /INSTALL /DEBUG /TITLE:"HP Updates" /NOREBOOT
RMDIR "c:\ssm" /s /q
exit 0
:Lenovo Updates
xcopy \\%TASKSERVER%\Share\Thininstaller c:\Thininstaller /S /H /I /Y
c:\Thininstaller\Thininstaller.exe /CM -search A -action INSTALL -repository \\%TASKSERVER%\Share\Repository-noicon -includerebootpackages 0,3 -showprogress -noreboot
RMDIR "c:\Thininstaller" /s /q
exit 0

Answer 1

The way these two driver management systems work is that the exe is not installed, only executed with different switches to look inside a share with drivers to match what is installed on the client and apply the missing drivers.
I have checked other threads with HP ssm and Lenovo Thininstaller regarding SCCM implementation and they all create a package for the exe and apply the command switches. Exactly as many of you already described here.
That works if you have only ONE share. I manage 3 shares, one for each geographical location that we prep Windows installations. This to make it faster for the client to download the drivers and to not use/load the WAN unnecessarily.
I read on another thread that I can't query a dp because it's assigned only when the client requires content. 
The only workaround as I see it is to:
1. Create 3 different packages with different  shares in the command line. And somehow apply a detection method in the task sequence to figure out location (DP, IP, DNS, boundary, Assigned Domain Controller).
2. Create 3 different packages and 3 different roles in MDT, one for every location. 
3. Only use one share on the location that mostly is used for Windows installations and accept that it will take longer for the drivers to be applied on the other locations. 
Which one should I go for?
Many of you may think that I should use the standard way of managing drivers in SCCM. But this is so much easier. I never have to package drivers or hardware applications like HP Connection Manager. I can reapply the package to any client in production and
update the drivers and model specific applications if needed.