Interesting situation was discovered today:
Scenario:
Roaming user ‘Fred’ is assigned to SS ‘A’ in England
Roaming user ‘Fred’ likes to roam and spends a lot of time in Ukraine at SS ‘B’
‘Fred’ likes to receive new software/patches and raises tickets to have these installed.
IT initiates SW deployment/install via CA which starts to download from SS ‘A’ when Fred is located at SS ‘B’ where the software has already been staged. The install occurs over the WAN and will take a lot longer eating up bandwidth over WAN.
Back in the days of SMS 2003 and I'm sure in SCCM you can configure boandaries for roaming clients. IP Subnets/Sites are configured and allocated and they could use the secondary SMS server that was closest. So I got hold of CA and asked the question if there is any configuration that you can do DM or client side that would set this automatically. This can be done manually using the command
caf setserveraddress <servername>
I was looking for an answer that was a bit more intelegent than having a user manually register to the nearest SS.
CA replied that there was a script 'location awareness script' that could be used. Unfortunately this came with all kinds of support implications and it was a 'high risk' script... basically - don't use it.
No comments:
Post a Comment