IT Management Suite

Hello Pablo!
> The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically)

Altiris does not have logics assigning machines to Site Servers based on Site Servers names.  In case there are some sites defined in your environment,  Software delivery requests of machines that are not assigned to any site are served either by PSes located in the NS Site (Site containing the subnet where NS is located) or by NS itself.

>  Is there any way to configure the behavior of unassigned clients
Here I assume you mean "agents unassigned to any site via subnet". Then one may assign agents to a site or a specific package server  via Manual Assignment  mechanism - see below (it is required to create a dedicated target of machines).  If it is Site Manual assignment, the machines will be served by PSes located in that Site.


However in the manual assignment case one should ensure all the packages that  potentially should be delivered to the manually assigned agents are stored on the assigned PSes as well. Dependent on you package assignment settings you must either assign a package to that Site via manual prestaging or assign packages to "All Package Servers" (which is probably an overkill).

Regards
Artur 

------------------------------
Software Engineer 5
Broadcom Inc.

Original Message:
Sent: Apr 14, 2023 04:22 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically). 

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)


Where those clients are going?


and AALB-ALTIRIS Site Server has manually configured the following IP addresses:


without any target assigned manually:


2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:


Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting to this particular one. Lets take as sample the first cleint, a Nigeria PC:

The client has the AALB-Altiris server assigned: 10.165.105.9 is the IP



that IP corresponds to IP range 10.165.105.0/28 assigned manually to Nigeria Oki Site Server:


But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select
   isnull(s.Name,'Not Assigned') as Sites
   ,vi.Name as [Subnet]
   ,COUNT(*) as [Node Count]
from vComputer vc
join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid
   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]
join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]
join vItem vi on vi.Guid = sub.Guid
left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid
left join vSite s on s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL
group by isnull(s.Name,'Not Assigned')
 ,vi.Name
order by isnull(s.Name,'Not Assigned')
 ,vi.Name

Thanks a lot in advance Arthur. 

Hello Pablo!
> The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically)

Altiris does not have logics assigning machines to Site Servers based on Site Servers names.  In case there are some sites defined in your environment,  Software delivery requests of machines that are not assigned to any site are served either by PSes located in the NS Site (Site containing the subnet where NS is located) or by NS itself.

>  Is there any way to configure the behavior of unassigned clients
Here I assume you mean "agents unassigned to any site via subnet". Then one may assign agents to a site or a specific package server  via Manual Assignment  mechanism - see below (it is required to create a dedicated target of machines).  If it is Site Manual assignment, the machines will be served by PSes located in that Site.


However in the manual assignment case one should ensure all the packages that  potentially should be delivered to the manually assigned agents are stored on the assigned PSes as well. Dependent on you package assignment settings you must either assign a package to that Site via manual prestaging or assign packages to "All Package Servers" (which is probably an overkill).

Regards
Artur 

------------------------------
Software Engineer 5
Broadcom Inc.

Original Message:
Sent: Apr 14, 2023 04:22 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically). 

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)


Where those clients are going?


and AALB-ALTIRIS Site Server has manually configured the following IP addresses:


without any target assigned manually:


2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:


Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting to this particular one. Lets take as sample the first cleint, a Nigeria PC:

The client has the AALB-Altiris server assigned: 10.165.105.9 is the IP



that IP corresponds to IP range 10.165.105.0/28 assigned manually to Nigeria Oki Site Server:


But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select
   isnull(s.Name,'Not Assigned') as Sites
   ,vi.Name as [Subnet]
   ,COUNT(*) as [Node Count]
from vComputer vc
join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid
   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]
join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]
join vItem vi on vi.Guid = sub.Guid
left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid
left join vSite s on s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL
group by isnull(s.Name,'Not Assigned')
 ,vi.Name
order by isnull(s.Name,'Not Assigned')
 ,vi.Name

Thanks a lot in advance Arthur. 

Hello Pablo!
> The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically)

Altiris does not have logics assigning machines to Site Servers based on Site Servers names.  In case there are some sites defined in your environment,  Software delivery requests of machines that are not assigned to any site are served either by PSes located in the NS Site (Site containing the subnet where NS is located) or by NS itself.

>  Is there any way to configure the behavior of unassigned clients
Here I assume you mean "agents unassigned to any site via subnet". Then one may assign agents to a site or a specific package server  via Manual Assignment  mechanism - see below (it is required to create a dedicated target of machines).  If it is Site Manual assignment, the machines will be served by PSes located in that Site.


However in the manual assignment case one should ensure all the packages that  potentially should be delivered to the manually assigned agents are stored on the assigned PSes as well. Dependent on you package assignment settings you must either assign a package to that Site via manual prestaging or assign packages to "All Package Servers" (which is probably an overkill).

Regards
Artur 

------------------------------
Software Engineer 5
Broadcom Inc.

Original Message:
Sent: Apr 14, 2023 04:22 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically). 

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)

Where are those clients going?

and AALB-ALTIRIS Site Server has manually configured the following IP addresses:

2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:

Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting this particular one. Let's take as sample the first client, a Nigeria PC

The client has the AALB-Altiris server assigned: the IP for example 10.165.105.9 is assigned to NGA_Jide_Oki:

But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select

   isnull(s.Name,'Not Assigned') as Sites

   ,vi.Name as [Subnet]

   ,COUNT(*) as [Node Count]

from vComputer vc

join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid

   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]

join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]

join vItem vi on vi.Guid = sub.Guid

left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid

left join vSite s on s.Guid = sm._ResourceGuid

WHERE s.Name IS NULL

group by isnull(s.Name,'Not Assigned')

 ,vi.Name

order by isnull(s.Name,'Not Assigned')

 ,vi.Name

Thanks a lot in advance Arthur.

Original Message:
Sent: Apr 17, 2023 04:52 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)


Where those clients are going?


and AALB-ALTIRIS Site Server has manually configured the following IP addresses:


without any target assigned manually:


2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:


Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting to this particular one. Lets take as sample the first cleint, a Nigeria PC:

The client has the AALB-Altiris server assigned: 10.165.105.9 is the IP



that IP corresponds to IP range 10.165.105.0/28 assigned manually to Nigeria Oki Site Server:


But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select
   isnull(s.Name,'Not Assigned') as Sites
   ,vi.Name as [Subnet]
   ,COUNT(*) as [Node Count]
from vComputer vc
join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid
   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]
join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]
join vItem vi on vi.Guid = sub.Guid
left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid
left join vSite s on s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL
group by isnull(s.Name,'Not Assigned')
 ,vi.Name
order by isnull(s.Name,'Not Assigned')
 ,vi.Name

Thanks a lot in advance Arthur. 

Original Message:
Sent: Apr 17, 2023 01:40 AM
From: Arthur Prosso
Subject: Clients with an IP unnasigned to any Site Server

Hello Pablo!
> The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically)

Altiris does not have logics assigning machines to Site Servers based on Site Servers names.  In case there are some sites defined in your environment,  Software delivery requests of machines that are not assigned to any site are served either by PSes located in the NS Site (Site containing the subnet where NS is located) or by NS itself.

>  Is there any way to configure the behavior of unassigned clients
Here I assume you mean "agents unassigned to any site via subnet". Then one may assign agents to a site or a specific package server  via Manual Assignment  mechanism - see below (it is required to create a dedicated target of machines).  If it is Site Manual assignment, the machines will be served by PSes located in that Site.


However in the manual assignment case one should ensure all the packages that  potentially should be delivered to the manually assigned agents are stored on the assigned PSes as well. Dependent on you package assignment settings you must either assign a package to that Site via manual prestaging or assign packages to "All Package Servers" (which is probably an overkill).

Regards
Artur 

------------------------------
Software Engineer 5
Broadcom Inc.

Original Message:
Sent: Apr 14, 2023 04:22 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically). 

Pablo, this is also happening to us.  Clients within subnets that we are not notified of are being assigned to the first site server in our list...alphabetically.  It used to be assigned to the site server in the same subnet as the SMP (which was ideal), but I believe back when 8.6 came out, that changed and they began to be assigned to the first in the list.  To work around this, I have set up a automation report to notify me when a bulk of clients are assigned to the alphabetically first site server in our list.  Then I use that list to properly assign to the correct location...it would be nice if this could be addressed.

Original Message:
Sent: Apr 17, 2023 04:58 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)

Where are those clients going?

and AALB-ALTIRIS Site Server has manually configured the following IP addresses:

2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:

Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting this particular one. Let's take as sample the first client, a Nigeria PC

The client has the AALB-Altiris server assigned: the IP for example 10.165.105.9 is assigned to NGA_Jide_Oki:

But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select

   isnull(s.Name,'Not Assigned') as Sites

   ,vi.Name as [Subnet]

   ,COUNT(*) as [Node Count]

from vComputer vc

join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid

   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]

join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]

join vItem vi on vi.Guid = sub.Guid

left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid

left join vSite s on s.Guid = sm._ResourceGuid

WHERE s.Name IS NULL

group by isnull(s.Name,'Not Assigned')

 ,vi.Name

order by isnull(s.Name,'Not Assigned')

 ,vi.Name

Thanks a lot in advance Arthur.

Original Message:
Sent: Apr 17, 2023 04:52 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)


Where those clients are going?


and AALB-ALTIRIS Site Server has manually configured the following IP addresses:


without any target assigned manually:


2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:


Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting to this particular one. Lets take as sample the first cleint, a Nigeria PC:

The client has the AALB-Altiris server assigned: 10.165.105.9 is the IP



that IP corresponds to IP range 10.165.105.0/28 assigned manually to Nigeria Oki Site Server:


But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select
   isnull(s.Name,'Not Assigned') as Sites
   ,vi.Name as [Subnet]
   ,COUNT(*) as [Node Count]
from vComputer vc
join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid
   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]
join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]
join vItem vi on vi.Guid = sub.Guid
left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid
left join vSite s on s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL
group by isnull(s.Name,'Not Assigned')
 ,vi.Name
order by isnull(s.Name,'Not Assigned')
 ,vi.Name

Thanks a lot in advance Arthur. 

Original Message:
Sent: Apr 17, 2023 01:40 AM
From: Arthur Prosso
Subject: Clients with an IP unnasigned to any Site Server

Hello Pablo!
> The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically)

Altiris does not have logics assigning machines to Site Servers based on Site Servers names.  In case there are some sites defined in your environment,  Software delivery requests of machines that are not assigned to any site are served either by PSes located in the NS Site (Site containing the subnet where NS is located) or by NS itself.

>  Is there any way to configure the behavior of unassigned clients
Here I assume you mean "agents unassigned to any site via subnet". Then one may assign agents to a site or a specific package server  via Manual Assignment  mechanism - see below (it is required to create a dedicated target of machines).  If it is Site Manual assignment, the machines will be served by PSes located in that Site.


However in the manual assignment case one should ensure all the packages that  potentially should be delivered to the manually assigned agents are stored on the assigned PSes as well. Dependent on you package assignment settings you must either assign a package to that Site via manual prestaging or assign packages to "All Package Servers" (which is probably an overkill).

Regards
Artur 

------------------------------
Software Engineer 5
Broadcom Inc.

Original Message:
Sent: Apr 14, 2023 04:22 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically). 

Thanks Arthur for your answer.

Actually, waht Im explaining is what is happening. 99% of clients with an IP that is not assigned to any site, because are within a IP range that has been created in any country without being previously notified to us, are connected to the first site server in the list. This is how Altiris is acting in our case. Maybe the theroy says that the behabiour is different, but in our case, is how Im explaining that is happening.

Why 99% of the unassigned IPs are contacting to the first SIte server from the list instead of any of the remaining SIte servers? African Ips and Erupean IPs going to UAE Server? (now to the new server located in Madrid?)

Originally the first Site server was UAE_Site_server and we decided to rename other server located in Madrid with higher specs in order to this new server embraces all those unassigned IPs, freeing the UAE SIte Server.

In fact, let me add that other clients that should go to the corresponing Site Server, when that Site Server is not available are going to the first Site Server of the list!

Let me add some screenshots:

1st Case - Unassigned IPs: IP range 10.48.202.0/24 (unknown IP range so not assigned to any Site Server)


Where those clients are going?


and AALB-ALTIRIS Site Server has manually configured the following IP addresses:


without any target assigned manually:


2nd case: Assigned IPs that are goiing to the first Site Server when the assigned one is not available

Same screenshot:


Clients coming from: Russia, Nigeria, UK, Ginea, Egypt, Spain, Switzerland.... going to this first site server, not other from the list. All of those clients have site servers located closely in terms of network, of course, but are contacting to this particular one. Lets take as sample the first cleint, a Nigeria PC:

The client has the AALB-Altiris server assigned: 10.165.105.9 is the IP



that IP corresponds to IP range 10.165.105.0/28 assigned manually to Nigeria Oki Site Server:


But as the serer was off in a particular moment, the clients arre going to the firs of the list.

The second server from the list, the UAE one only has IPs corresponding to UAE and the same with the rest of servers.

On the other hand, I think that is a good idea to create a target detecting dinamically the IPs not assigned and adding that target to the Site sever that we decide. Could you please help with the bet Query for the filter? COuld be the following one?

select
   isnull(s.Name,'Not Assigned') as Sites
   ,vi.Name as [Subnet]
   ,COUNT(*) as [Node Count]
from vComputer vc
join Inv_AeX_AC_TCPIP ip on ip._ResourceGuid = vc.Guid
   and ip.[IP Address] = vc.[IP Address] and ip.[MAC Address] = vc.[MAC Address]
join vSubnet sub on sub.Subnet = ip.Subnet and sub.[Subnet Mask] = ip.[Subnet Mask]
join vItem vi on vi.Guid = sub.Guid
left join vSiteSubnetMap sm on sm.SubnetGuid = sub.Guid
left join vSite s on s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL
group by isnull(s.Name,'Not Assigned')
 ,vi.Name
order by isnull(s.Name,'Not Assigned')
 ,vi.Name

Thanks a lot in advance Arthur. 

Hello Pablo!
> The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically)

Altiris does not have logics assigning machines to Site Servers based on Site Servers names.  In case there are some sites defined in your environment,  Software delivery requests of machines that are not assigned to any site are served either by PSes located in the NS Site (Site containing the subnet where NS is located) or by NS itself.

>  Is there any way to configure the behavior of unassigned clients
Here I assume you mean "agents unassigned to any site via subnet". Then one may assign agents to a site or a specific package server  via Manual Assignment  mechanism - see below (it is required to create a dedicated target of machines).  If it is Site Manual assignment, the machines will be served by PSes located in that Site.


However in the manual assignment case one should ensure all the packages that  potentially should be delivered to the manually assigned agents are stored on the assigned PSes as well. Dependent on you package assignment settings you must either assign a package to that Site via manual prestaging or assign packages to "All Package Servers" (which is probably an overkill).

Regards
Artur 

------------------------------
Software Engineer 5
Broadcom Inc.

Original Message:
Sent: Apr 14, 2023 04:22 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

The problem is with clients that have any IP unassigned, meaning that the IPs are not within any IP range that has been previously assigned to any specific Site Server. In this case, the Altiris behaviour is to assign to those clients the first SIte Server from the Site Server list (ordered alphabetically). 

Hi Pablo Llorente and Jeff Stanton!

Jeff Stanton: Clients within subnets that we are not notified of are being assigned to the first site server in our list...alphabetically.  It used to be assigned to the site server in the same subnet as the SMP (which was ideal), but I believe back when 8.6 came out, that changed and they began to be assigned to the first in the list.

IP: I used clean installed client 8.6 RU3 (This client computer is from subnet that isn't included in any existing Site(s) on NS where Task Servers are running). 
According to functionality, Client Task Agent asks NS to offer list of available Task Servers and then order them by their available shares.
As result we see that CTA got Task Server for registration where more free server shares (Not alphabetically)

This is a default setting which is used by CTA to register with available Task Servers

Note:
By default, new clean installed Symantec Management Agent on client computer, will attempt to register Client task agent with task servers, using "Choose the Task Server relative to the remaining capacity of each server" option (if this client computer didn't yet receive client policies but "Task Agent Settings" policy has another option enabled)

In case if there is another option enabled in "Task Agent Settings" policy, then this new installed client computer must refresh policy to receive these settings, then CTA will act according to set option for further registration with Task Servers

2. Pablo Llorente: But the idea about the target could be good
IP: Here is your modified SQL Query to create a filter and see list of computers which do not have any Site assignment by their subnet(s)

SELECT
    vc.Guid
FROM vComputer vc
JOIN Inv_AeX_AC_TCPIP ip ON ip._ResourceGuid = vc.Guid
   AND ip.[IP Address] = vc.[IP Address] AND ip.[MAC Address] = vc.[MAC Address]
JOIN vSubnet sub ON sub.Subnet = ip.Subnet AND sub.[Subnet Mask] = ip.[Subnet Mask]
JOIN vItem vi ON vi.Guid = sub.Guid
LEFT JOIN vSiteSubnetMap sm ON sm.SubnetGuid = sub.Guid
LEFT JOIN vSite s ON s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL

Note:
1. Custom filter which is used in custom resource target, will be updated by "Delta Membership Update" scheduled task on NS only if this resource target is included in any existing and enabled policy. Otherwise resource target will be fully updated by next "Complete Update Membership" scheduled task on NS.

2. In case if there are new subnet(s) appear in NS database from new arrived client computers basic inventory, they will be populated on "Subnets" page only after default scheduled task execution "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" or user can manually force subnets synchronization (If synchronization isn't yet done for new arrived subnets from new client computers without Site(s), then custom filter will doesn't populate these new subnet(s) for new client computers without site assignments)

Best regards,
IP.

Also here is detailed information about how Client Task Agent and Task Servers registration works
https://knowledge.broadcom.com/external/article/150990/client-task-agent-connectivity.html

"Site Servers" report shows information, what Site Servers are assigned for "Default Internet Site" to serve CEM agents with different subnets

Hi Pablo Llorente and Jeff Stanton!

Jeff Stanton: Clients within subnets that we are not notified of are being assigned to the first site server in our list...alphabetically.  It used to be assigned to the site server in the same subnet as the SMP (which was ideal), but I believe back when 8.6 came out, that changed and they began to be assigned to the first in the list.

IP: I used clean installed client 8.6 RU3 (This client computer is from subnet that isn't included in any existing Site(s) on NS where Task Servers are running). 
According to functionality, Client Task Agent asks NS to offer list of available Task Servers and then order them by their available shares.
As result we see that CTA got Task Server for registration where more free server shares (Not alphabetically)

This is a default setting which is used by CTA to register with available Task Servers

Note:
By default, new clean installed Symantec Management Agent on client computer, will attempt to register Client task agent with task servers, using "Choose the Task Server relative to the remaining capacity of each server" option (if this client computer didn't yet receive client policies but "Task Agent Settings" policy has another option enabled)

In case if there is another option enabled in "Task Agent Settings" policy, then this new installed client computer must refresh policy to receive these settings, then CTA will act according to set option for further registration with Task Servers

2. Pablo Llorente: But the idea about the target could be good
IP: Here is your modified SQL Query to create a filter and see list of computers which do not have any Site assignment by their subnet(s)

SELECT
    vc.Guid
FROM vComputer vc
JOIN Inv_AeX_AC_TCPIP ip ON ip._ResourceGuid = vc.Guid
   AND ip.[IP Address] = vc.[IP Address] AND ip.[MAC Address] = vc.[MAC Address]
JOIN vSubnet sub ON sub.Subnet = ip.Subnet AND sub.[Subnet Mask] = ip.[Subnet Mask]
JOIN vItem vi ON vi.Guid = sub.Guid
LEFT JOIN vSiteSubnetMap sm ON sm.SubnetGuid = sub.Guid
LEFT JOIN vSite s ON s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL

Note:
1. Custom filter which is used in custom resource target, will be updated by "Delta Membership Update" scheduled task on NS only if this resource target is included in any existing and enabled policy. Otherwise resource target will be fully updated by next "Complete Update Membership" scheduled task on NS.

2. In case if there are new subnet(s) appear in NS database from new arrived client computers basic inventory, they will be populated on "Subnets" page only after default scheduled task execution "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" or user can manually force subnets synchronization (If synchronization isn't yet done for new arrived subnets from new client computers without Site(s), then custom filter will doesn't populate these new subnet(s) for new client computers without site assignments)

Best regards,
IP.

Original Message:
Sent: Apr 17, 2023 04:54 AM
From: Pablo Llorente
Subject: Clients with an IP unnasigned to any Site Server

Note:

The screenshots are not visible in the email but are correct checking the
thread in the broadcom portal.


Best Regards / Saludos
___________________________

PABLO LLORENTE ABAD
EMEA Workplace Services , Workplace Specialist

Calle Albasanz 14, 4th floor
Madrid , Spain
Mobile +34 672746460
*pablo.llorente@holcim.com

Hi Pablo Llorente and Jeff Stanton!

Jeff Stanton: Clients within subnets that we are not notified of are being assigned to the first site server in our list...alphabetically.  It used to be assigned to the site server in the same subnet as the SMP (which was ideal), but I believe back when 8.6 came out, that changed and they began to be assigned to the first in the list.

IP: I used clean installed client 8.6 RU3 (This client computer is from subnet that isn't included in any existing Site(s) on NS where Task Servers are running). 
According to functionality, Client Task Agent asks NS to offer list of available Task Servers and then order them by their available shares.
As result we see that CTA got Task Server for registration where more free server shares (Not alphabetically)

This is a default setting which is used by CTA to register with available Task Servers

Note:
By default, new clean installed Symantec Management Agent on client computer, will attempt to register Client task agent with task servers, using "Choose the Task Server relative to the remaining capacity of each server" option (if this client computer didn't yet receive client policies but "Task Agent Settings" policy has another option enabled)

In case if there is another option enabled in "Task Agent Settings" policy, then this new installed client computer must refresh policy to receive these settings, then CTA will act according to set option for further registration with Task Servers

2. Pablo Llorente: But the idea about the target could be good
IP: Here is your modified SQL Query to create a filter and see list of computers which do not have any Site assignment by their subnet(s)

SELECT
    vc.Guid
FROM vComputer vc
JOIN Inv_AeX_AC_TCPIP ip ON ip._ResourceGuid = vc.Guid
   AND ip.[IP Address] = vc.[IP Address] AND ip.[MAC Address] = vc.[MAC Address]
JOIN vSubnet sub ON sub.Subnet = ip.Subnet AND sub.[Subnet Mask] = ip.[Subnet Mask]
JOIN vItem vi ON vi.Guid = sub.Guid
LEFT JOIN vSiteSubnetMap sm ON sm.SubnetGuid = sub.Guid
LEFT JOIN vSite s ON s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL

Note:
1. Custom filter which is used in custom resource target, will be updated by "Delta Membership Update" scheduled task on NS only if this resource target is included in any existing and enabled policy. Otherwise resource target will be fully updated by next "Complete Update Membership" scheduled task on NS.

2. In case if there are new subnet(s) appear in NS database from new arrived client computers basic inventory, they will be populated on "Subnets" page only after default scheduled task execution "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" or user can manually force subnets synchronization (If synchronization isn't yet done for new arrived subnets from new client computers without Site(s), then custom filter will doesn't populate these new subnet(s) for new client computers without site assignments)

Best regards,
IP.

Hi Igor,
about this point :

2. In case if there are new subnet(s) appear in NS database from new arrived client computers basic inventory, they will be populated on "Subnets" page only after default scheduled task execution "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" or user can manually force subnets synchronization (If synchronization isn't yet done for new arrived subnets from new client computers without Site(s), then custom filter will doesn't populate these new subnet(s) for new client computers without site assignmen
       Before "re-synchronize subnets," if we could have some opportunity to link those new subnets with sites based in batches, the effort to fix the collateral effects probably will decrease. Unfortunately, the interface "assign to site" is very simple and doesn't permit the use of targets, for example, to extract subnets and link with sites manually created.
Do you know another way to make the same using queries or the ASDK?
We are talking about thousands of new subnets; in that case, that approach can decrease a herculean manual intervention.
Thanks in advance!

Hi Pablo Llorente and Jeff Stanton!

Jeff Stanton: Clients within subnets that we are not notified of are being assigned to the first site server in our list...alphabetically.  It used to be assigned to the site server in the same subnet as the SMP (which was ideal), but I believe back when 8.6 came out, that changed and they began to be assigned to the first in the list.

IP: I used clean installed client 8.6 RU3 (This client computer is from subnet that isn't included in any existing Site(s) on NS where Task Servers are running). 
According to functionality, Client Task Agent asks NS to offer list of available Task Servers and then order them by their available shares.
As result we see that CTA got Task Server for registration where more free server shares (Not alphabetically)

This is a default setting which is used by CTA to register with available Task Servers

Note:
By default, new clean installed Symantec Management Agent on client computer, will attempt to register Client task agent with task servers, using "Choose the Task Server relative to the remaining capacity of each server" option (if this client computer didn't yet receive client policies but "Task Agent Settings" policy has another option enabled)

In case if there is another option enabled in "Task Agent Settings" policy, then this new installed client computer must refresh policy to receive these settings, then CTA will act according to set option for further registration with Task Servers

2. Pablo Llorente: But the idea about the target could be good
IP: Here is your modified SQL Query to create a filter and see list of computers which do not have any Site assignment by their subnet(s)

SELECT
    vc.Guid
FROM vComputer vc
JOIN Inv_AeX_AC_TCPIP ip ON ip._ResourceGuid = vc.Guid
   AND ip.[IP Address] = vc.[IP Address] AND ip.[MAC Address] = vc.[MAC Address]
JOIN vSubnet sub ON sub.Subnet = ip.Subnet AND sub.[Subnet Mask] = ip.[Subnet Mask]
JOIN vItem vi ON vi.Guid = sub.Guid
LEFT JOIN vSiteSubnetMap sm ON sm.SubnetGuid = sub.Guid
LEFT JOIN vSite s ON s.Guid = sm._ResourceGuid
WHERE s.Name IS NULL

Note:
1. Custom filter which is used in custom resource target, will be updated by "Delta Membership Update" scheduled task on NS only if this resource target is included in any existing and enabled policy. Otherwise resource target will be fully updated by next "Complete Update Membership" scheduled task on NS.

2. In case if there are new subnet(s) appear in NS database from new arrived client computers basic inventory, they will be populated on "Subnets" page only after default scheduled task execution "NS.Package Refresh.{bd6bf880-bfae-4dad-b746-e8be99f3b8a8}" or user can manually force subnets synchronization (If synchronization isn't yet done for new arrived subnets from new client computers without Site(s), then custom filter will doesn't populate these new subnet(s) for new client computers without site assignments)

Best regards,
IP.