[mssms] Easy way to add/remove all packages from DPs?

2017-05-03 Thread ODONNELL Aaron M
We are in the process of replacing some servers that host our distribution 
points. The new hardware is in place, right next to the old servers which will 
still be active until they're ready to be decommissioned. Is there a powershell 
(or some other automated way) to remove all packages from a distribution point? 
I'm hoping to save a million or so clicks and not be forced into going into 
every single application/package properties and removing them from the old DP 
and then adding it to the new ones.


Thanks,

Aaron O'Donnell
ODOT Information Systems
[email flying-t]






[mssms] RE: Proxy Management Point and Boundary behavior post 1610

2017-05-03 Thread Jason Sandys
For the preference, no, I mean subnet. Just as is depicted in that older 
flowchart. The client will order all DPs in all of its boundary groups by 
certain things and the first is subnet.

We weren’t 100% sure on removing the DP from the secondary site server. I 
thought it couldn’t be done in a supported way and he thought it could be. I’m 
not sure which is the correct answer here. I now an MP can’t be removed. Never 
tried a DP though.

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Burke, John
Sent: Wednesday, May 3, 2017 2:35 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

Thanks for the info Jason,

could you clarify these though, just so im sure?

  *
  *   Since DPs in the same subnet are preferred, the remote DP could be placed 
in the same subnet as the clients at that same remote location. – You mean 
boundary Group here I hope? We have 1000s of subnets across multiple forests. 
The remote dp’s are in the same boundary group – but that has a few 100 ip 
range boundaries. 2007 we used to use AD sites but Microsoft told us not to mix 
and to go with IP Ranges now.

Remove the DP from the secondary site server and use an additional site system 
for the DP role at the same location as the secondary site server. – So  Dev 
confirmed this config would be supported? “You cannot remove the DP or MP role 
from a secondary site server (at least not in a supported way).”





From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: May-03-17 3:25 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610


So I just talked to one of the devs and he confirmed what I’ve said. Today, 
there is no way to separate the DP from the MP when specifying the site system 
associated with a boundary group. Thus, this is a shortcoming in the current 
design. You have two potential ways to address this scenario today:


  *   Since DPs in the same subnet are preferred, the remote DP could be placed 
in the same subnet as the clients at that same remote location.
  *   Remove the DP from the secondary site server and use an additional site 
system for the DP role at the same location as the secondary site server.



We talked through the scenario though and the dev understood it and why they 
can’t do anything else today. *Today* of course is a keyword here though and he 
feels that planned improvements in near future releases will address this. No 
guarantees and no specifics of course (as that’s all NDA).



As for documentation, you can suggest (and even contribute to) all of the 
current branch documentation hosted on docs.microsoft.com.



For lots more details and fun with boundary groups (more fun than fun with 
flags even) come to our session (Kerim and myself) at MMS on Boundary Groups.



J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Burke, John
Sent: Wednesday, May 3, 2017 8:54 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

Thanks.

I think Microsoft needs to get some updated documents similar to those you 
provided but updated.  The flow chart one would be fantastic.  I see now way to 
get it working properly  without throwing out the entire design.

So we did set up a secondary site because we wanted MOST of the traffic to flow 
to the secondary site.  That was the entire reason we went with a secondary 
site.  We then set up a bunch of DP’s  across multiple wan areas that we wanted 
to flow to that server (even though I know it sends a few things up to the 
primary MP Most traffic went to our secondary site)

So just before this update – we had 1 Secondary server MP + DP.  Then we had 3 
other servers setup across fairly well connected wans (Each in their own 
boundary group with 1 server + relationship)  that serviced a few 1000 pc’s.  
The Systems all used those DPs’ locally and the Secondary Sites Server was set 
up as a fallback.  This worked really well and when you went to the console – 
you could see all those clients withint that boundary group  was set to that 
Secondary Site MP.

Example – Atlantic Secondary Site Boundary group – 1 server no relationship  - 
all atlantic boundaries –ip ranges
New Brunswick boundary group – 1 server 1 relationshp to atlantic – NB Ip ranges
Nova Scotia boundary group - 1 server 1 relationshp to atlantic – NS Ip ranges
Newfoundland boundary group -1 server 1 relationshp to atlantic – NL Ip ranges


Now after the change it seems no matter what we do – the clients all show up 
with our primary site MP (and it seems all traffic around policy and inventory 
and status messages is going there)

When we created 

[mssms] RE: Upgrade Readiness with System Center Configuration Manager

2017-05-03 Thread Daniel Ratliff
FYI Dave, Microsoft fixed the return code issue with v1.8 of the script, 
released last month.

https://blogs.technet.microsoft.com/upgradeanalytics/2017/04/07/new-version-of-the-upgrade-readiness-deployment-script-version-1-8-is-now-available/

Daniel Ratliff

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Dave West
Sent: Tuesday, May 2, 2017 7:51 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Upgrade Readiness with System Center Configuration Manager

Just to let you all know we have successfully implemented Upgrade Readiness 
with System Center Configuration Manager.

The documentation is not great (hasn't been updated to reflect recent changes) 
and there doesn't seem to be a single end-to-end document from Microsoft, but 
we found a great article by Nickolaj Andersen and it mostly matched the process 
we needed to follow:

Setup a connection between Upgrade Analytics and ConfigMgr Current 
Branch

Some noteworthy points are:

* The OMS workspace can be specifically configured with the 'Free' data 
plan (500MB daily upload limit, 7 day data retention, 90 day activity log and 
500min/month runbooks)

* Make sure you assign the App permissions to the resource group and 
the OMS workspace

* We found although the documentation says the script will return exit 
codes, it does not in all cases e.g. returns 0 if a pending reboot is required 
(not very helpful) so we made some minor tweaks to the PowerShell script to 
ensure the our detection rules and return codes were meaningful in ConfigMgr

* When you run the script it can take around 48 hours before the data 
is visible in OMS

* The ConfigMgr connector has a default weekly synchronisation schedule 
so it can take 7 days before ConfigMgr gets the data after OMS

Dave

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West
Sent: 12 April 2017 15:45
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Upgrade Readiness with System Center Configuration Manager

Thanks for the info, we will look into this and let you all know how we get on.

Dave

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff
Sent: 11 April 2017 13:09
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Upgrade Readiness with System Center Configuration Manager

We are using it. It's very simple to setup. All you need is a free OMS account, 
and an Azure Subscription.

Once you setup your Azure Subscription, make sure you go into the Azure Portal 
and change the subscription to Pay as you go. We confirmed with our TAM and an 
Azure SME that there is no cost as long as the only service you add in OMS is 
Upgrade Readiness.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl
Sent: Tuesday, April 11, 2017 7:54 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Upgrade Readiness with System Center Configuration Manager

I am also interested in this, and are in a similar situation where we have an 
O365 tenant but no Azure per say. I spoke to MS rep and he said that the log 
analytics ingestion service as you describe is free, you will need a CC to sign 
up though. I have not pursued this as I am hoping my company will setup a full 
Azure footprint very soon. We also have some telemetry data challenges with our 
EU side of the business we have to work out first.

Please let me know if you go down this road and what exactly was needed.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West
Sent: Tuesday, April 11, 2017 4:25 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Upgrade Readiness with System Center Configuration Manager

I was wondering if anyone has integrated Upgrade Readiness with System Center 
Configuration Manager?

https://docs.microsoft.com/en-gb/sccm/core/clients/manage/upgrade/upgrade-analytics

We are looking into this now and there is a requirement for Microsoft 
Operations Management Suite (OMS) for the log analytics, and I can't seem to 
find any mention of the cost of adding OMS, specifically the log analytics, 
required for Upgrade Readiness/Upgrade Analytics Connector in ConfigMgr.

We have an Office365 tenancy but no Azure AD etc. so I was wondering if anyone 
else has set this up and if so how did they handle the OMS side of things.

Dave West
Senior Operations Analyst
Service Management
Technology & Information Services | Plymouth University | Drake Circus | 
Plymouth | PL4 8AA

[mssms] RE: Proxy Management Point and Boundary behavior post 1610

2017-05-03 Thread Burke, John
Thanks for the info Jason,

could you clarify these though, just so im sure?

  *
  *   Since DPs in the same subnet are preferred, the remote DP could be placed 
in the same subnet as the clients at that same remote location. – You mean 
boundary Group here I hope? We have 1000s of subnets across multiple forests. 
The remote dp’s are in the same boundary group – but that has a few 100 ip 
range boundaries. 2007 we used to use AD sites but Microsoft told us not to mix 
and to go with IP Ranges now.

Remove the DP from the secondary site server and use an additional site system 
for the DP role at the same location as the secondary site server. – So  Dev 
confirmed this config would be supported? “You cannot remove the DP or MP role 
from a secondary site server (at least not in a supported way).”





From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Jason Sandys
Sent: May-03-17 3:25 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610


So I just talked to one of the devs and he confirmed what I’ve said. Today, 
there is no way to separate the DP from the MP when specifying the site system 
associated with a boundary group. Thus, this is a shortcoming in the current 
design. You have two potential ways to address this scenario today:


  *   Since DPs in the same subnet are preferred, the remote DP could be placed 
in the same subnet as the clients at that same remote location.
  *   Remove the DP from the secondary site server and use an additional site 
system for the DP role at the same location as the secondary site server.



We talked through the scenario though and the dev understood it and why they 
can’t do anything else today. *Today* of course is a keyword here though and he 
feels that planned improvements in near future releases will address this. No 
guarantees and no specifics of course (as that’s all NDA).



As for documentation, you can suggest (and even contribute to) all of the 
current branch documentation hosted on docs.microsoft.com.



For lots more details and fun with boundary groups (more fun than fun with 
flags even) come to our session (Kerim and myself) at MMS on Boundary Groups.



J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Burke, John
Sent: Wednesday, May 3, 2017 8:54 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

Thanks.

I think Microsoft needs to get some updated documents similar to those you 
provided but updated.  The flow chart one would be fantastic.  I see now way to 
get it working properly  without throwing out the entire design.

So we did set up a secondary site because we wanted MOST of the traffic to flow 
to the secondary site.  That was the entire reason we went with a secondary 
site.  We then set up a bunch of DP’s  across multiple wan areas that we wanted 
to flow to that server (even though I know it sends a few things up to the 
primary MP Most traffic went to our secondary site)

So just before this update – we had 1 Secondary server MP + DP.  Then we had 3 
other servers setup across fairly well connected wans (Each in their own 
boundary group with 1 server + relationship)  that serviced a few 1000 pc’s.  
The Systems all used those DPs’ locally and the Secondary Sites Server was set 
up as a fallback.  This worked really well and when you went to the console – 
you could see all those clients withint that boundary group  was set to that 
Secondary Site MP.

Example – Atlantic Secondary Site Boundary group – 1 server no relationship  - 
all atlantic boundaries –ip ranges
New Brunswick boundary group – 1 server 1 relationshp to atlantic – NB Ip ranges
Nova Scotia boundary group - 1 server 1 relationshp to atlantic – NS Ip ranges
Newfoundland boundary group -1 server 1 relationshp to atlantic – NL Ip ranges


Now after the change it seems no matter what we do – the clients all show up 
with our primary site MP (and it seems all traffic around policy and inventory 
and status messages is going there)

When we created a new boundary group – added all the boundaries and added the 
Secondary site to that – then poof – we now have NO WAY to really control which 
DP the clients in those 3 other wans use.

That flow chart is nice and very clear but it’s also talking about the days 
when it all made sense – and we had Protected DP’s and so on.  If I could set 
that option it would be fantastic because I’d  just tick that off and it the 
clients would all be happy.  I can’t find any documentation that tells me it 
will prefer the DP’s in those  in the remote region boundary groups.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: May-02-17 4:52 PM
To: 

[mssms] RE: Proxy Management Point and Boundary behavior post 1610

2017-05-03 Thread Jason Sandys
So I just talked to one of the devs and he confirmed what I’ve said. Today, 
there is no way to separate the DP from the MP when specifying the site system 
associated with a boundary group. Thus, this is a shortcoming in the current 
design. You have two potential ways to address this scenario today:


  *   Since DPs in the same subnet are preferred, the remote DP could be placed 
in the same subnet as the clients at that same remote location.
  *   Remove the DP from the secondary site server and use an additional site 
system for the DP role at the same location as the secondary site server.



We talked through the scenario though and the dev understood it and why they 
can’t do anything else today. *Today* of course is a keyword here though and he 
feels that planned improvements in near future releases will address this. No 
guarantees and no specifics of course (as that’s all NDA).



As for documentation, you can suggest (and even contribute to) all of the 
current branch documentation hosted on docs.microsoft.com.



For lots more details and fun with boundary groups (more fun than fun with 
flags even) come to our session (Kerim and myself) at MMS on Boundary Groups.



J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Burke, John
Sent: Wednesday, May 3, 2017 8:54 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

Thanks.

I think Microsoft needs to get some updated documents similar to those you 
provided but updated.  The flow chart one would be fantastic.  I see now way to 
get it working properly  without throwing out the entire design.

So we did set up a secondary site because we wanted MOST of the traffic to flow 
to the secondary site.  That was the entire reason we went with a secondary 
site.  We then set up a bunch of DP’s  across multiple wan areas that we wanted 
to flow to that server (even though I know it sends a few things up to the 
primary MP Most traffic went to our secondary site)

So just before this update – we had 1 Secondary server MP + DP.  Then we had 3 
other servers setup across fairly well connected wans (Each in their own 
boundary group with 1 server + relationship)  that serviced a few 1000 pc’s.  
The Systems all used those DPs’ locally and the Secondary Sites Server was set 
up as a fallback.  This worked really well and when you went to the console – 
you could see all those clients withint that boundary group  was set to that 
Secondary Site MP.

Example – Atlantic Secondary Site Boundary group – 1 server no relationship  - 
all atlantic boundaries –ip ranges
New Brunswick boundary group – 1 server 1 relationshp to atlantic – NB Ip ranges
Nova Scotia boundary group - 1 server 1 relationshp to atlantic – NS Ip ranges
Newfoundland boundary group -1 server 1 relationshp to atlantic – NL Ip ranges


Now after the change it seems no matter what we do – the clients all show up 
with our primary site MP (and it seems all traffic around policy and inventory 
and status messages is going there)

When we created a new boundary group – added all the boundaries and added the 
Secondary site to that – then poof – we now have NO WAY to really control which 
DP the clients in those 3 other wans use.

That flow chart is nice and very clear but it’s also talking about the days 
when it all made sense – and we had Protected DP’s and so on.  If I could set 
that option it would be fantastic because I’d  just tick that off and it the 
clients would all be happy.  I can’t find any documentation that tells me it 
will prefer the DP’s in those  in the remote region boundary groups.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: May-02-17 4:52 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

> “I’ve been told by our network folks that the clients are all going up to our 
> primary MP UNLESS we add the proxy management point – secondary site – within 
> the boundary group.”

Correct. Clients use a secondary site based upon content location boundary 
groups: https://home.configmgrftw.com/secondary-sites-and-boundary-groups/

Site assignment has nothing to do with the use of roles within a secondary site.

Do keep in mind though that *all* clients must always be able to access an MP 
within the primary site whether or not they are part of a secondary site.

> ” This will likely mean all my regional boxes will end up also using it as a 
> DP unfortunately”

Not necessarily. I can’t find a specific reference in the [current] 
documentation, not that there isn’t one, I just can’t it right now, but clients 
do order DPs in the list returned from the MP based upon IP Subnet and AD Site. 
This is an older flowchart that depicts this: 
https://technet.microsoft.com/en-us/library/bb932150.aspx


RE: [mssms] RE: Current Branch have something Similar to "computer details" from 2007?

2017-05-03 Thread Burke, John
I’ve also noticed there is not even a canned report for what deployments and 
status for a computer in Current Branch.

This current branch is almost starting to feel like a downgrade.

Why no Computer Details  report or dashboard canned in with newer update 1710.

I attempted to get those queries working but even just pulling out select it 
didn’t work. I’d have to be a pile more handy with sQl to get it working I 
think.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Sherry Kissinger
Sent: April-24-17 5:57 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] RE: Current Branch have something Similar to "computer 
details" from 2007?

the RDL presumes you have all the other stuff--which you may not.
What you can do is that RDL is really just a text file.  Just look at it in 
notepad, search for "Select"... and then steal as many of the sql statements as 
you can and make your own.

On Mon, Apr 24, 2017 at 2:29 PM, Burke, John 
> wrote:
Hi folks,

I did attempt to bring in that RDL for computer details and it blew up.  I’m 
wondering if anyone knows of a location of reports that can be pulled in?

The ones below look great if I could have gotten them working.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] 
On Behalf Of Sherry Kissinger
Sent: November-30-16 4:37 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] RE: Current Branch have something Similar to "computer 
details" from 2007?

not as cool as what hackathon did I'm sure; but way back when... 
http://www.madisonusergroup.com/2012/11/28/octobernovember-2012-meeting-notes/

It was mostly about making a cool-LOOKING report; but the guts of a "all in 
one" type of SSRS report for a specific computer by name is in there.

On Wed, Nov 30, 2016 at 1:42 PM, Burke, John 
> wrote:
Thanks.

Not something that can be Hacked in before hand? ☺

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] 
On Behalf Of Daniel Ratliff
Sent: November-30-16 11:55 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Current Branch have something Similar to "computer 
details" from 2007?

Hopefully coming in 1702/1703. A pretty awesome client dashboard was put 
together in the hackathon at the MVP Summit a few weeks ago.

Daniel Ratliff

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Burke, John
Sent: Wednesday, November 30, 2016 10:23 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Current Branch have something Similar to "computer details" 
from 2007?

https://technet.microsoft.com/en-ca/library/bb633263.aspx

Hi,

I use this every day in 2007.  I’m wondering if I’m just missing where to find 
something similar in current branch.


The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.





--
Thank you,

Sherry Kissinger

My Parameters:  Standardize. Simplify. Automate
Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, 
http://www.smguru.org





--
Thank you,

Sherry Kissinger

My Parameters:  Standardize. Simplify. Automate
Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, 
http://www.smguru.org




[mssms] RE: Proxy Management Point and Boundary behavior post 1610

2017-05-03 Thread Burke, John
Thanks.

I think Microsoft needs to get some updated documents similar to those you 
provided but updated.  The flow chart one would be fantastic.  I see now way to 
get it working properly  without throwing out the entire design.

So we did set up a secondary site because we wanted MOST of the traffic to flow 
to the secondary site.  That was the entire reason we went with a secondary 
site.  We then set up a bunch of DP’s  across multiple wan areas that we wanted 
to flow to that server (even though I know it sends a few things up to the 
primary MP Most traffic went to our secondary site)

So just before this update – we had 1 Secondary server MP + DP.  Then we had 3 
other servers setup across fairly well connected wans (Each in their own 
boundary group with 1 server + relationship)  that serviced a few 1000 pc’s.  
The Systems all used those DPs’ locally and the Secondary Sites Server was set 
up as a fallback.  This worked really well and when you went to the console – 
you could see all those clients withint that boundary group  was set to that 
Secondary Site MP.

Example – Atlantic Secondary Site Boundary group – 1 server no relationship  - 
all atlantic boundaries –ip ranges
New Brunswick boundary group – 1 server 1 relationshp to atlantic – NB Ip ranges
Nova Scotia boundary group - 1 server 1 relationshp to atlantic – NS Ip ranges
Newfoundland boundary group -1 server 1 relationshp to atlantic – NL Ip ranges


Now after the change it seems no matter what we do – the clients all show up 
with our primary site MP (and it seems all traffic around policy and inventory 
and status messages is going there)

When we created a new boundary group – added all the boundaries and added the 
Secondary site to that – then poof – we now have NO WAY to really control which 
DP the clients in those 3 other wans use.

That flow chart is nice and very clear but it’s also talking about the days 
when it all made sense – and we had Protected DP’s and so on.  If I could set 
that option it would be fantastic because I’d  just tick that off and it the 
clients would all be happy.  I can’t find any documentation that tells me it 
will prefer the DP’s in those  in the remote region boundary groups.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Jason Sandys
Sent: May-02-17 4:52 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

> “I’ve been told by our network folks that the clients are all going up to our 
> primary MP UNLESS we add the proxy management point – secondary site – within 
> the boundary group.”

Correct. Clients use a secondary site based upon content location boundary 
groups: https://home.configmgrftw.com/secondary-sites-and-boundary-groups/

Site assignment has nothing to do with the use of roles within a secondary site.

Do keep in mind though that *all* clients must always be able to access an MP 
within the primary site whether or not they are part of a secondary site.

> ” This will likely mean all my regional boxes will end up also using it as a 
> DP unfortunately”

Not necessarily. I can’t find a specific reference in the [current] 
documentation, not that there isn’t one, I just can’t it right now, but clients 
do order DPs in the list returned from the MP based upon IP Subnet and AD Site. 
This is an older flowchart that depicts this: 
https://technet.microsoft.com/en-us/library/bb932150.aspx

You cannot remove the DP or MP role from a secondary site server (at least not 
in a supported way).

J


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Burke, John
Sent: Tuesday, May 2, 2017 10:01 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Proxy Management Point and Boundary behavior post 1610

Short term I had to go to my boundary group for my secondary site and I added 
all those subnets.

This will likely mean all my regional boxes will end up also using it as a DP 
unfortunately Unless the clients somehow know to use the other boundary group 
DP they are assigned to because of the relationship pointing up to the 
secondary site server MP DP.



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Burke, John
Sent: May-02-17 10:25 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Proxy Management Point and Boundary behavior post 1610

Hi,

We upgraded from 1606 to 1610 to 1702 and trying to get a handle on the 
boundary changes.
I’ve been told by our network folks that the clients are all going up to our 
primary MP UNLESS we add the proxy management point – secondary site – within 
the boundary group.


We wanted to have systems in an area use DP’s in their local area first, and 
fall back to secondary site server DP for software AND go the secondary site 

[mssms] RE: 1702 - Software Center settings and notification messages for high-impact task sequences

2017-05-03 Thread Kent, Mark
Did your clients update to the latest agent?

Mark Kent
Manager, Client Systems Engineering
Technology Support Services
Resources for Information, Technology and Education (RITE)
http://rite.buffalostate.edu

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Enley, Carl
Sent: Wednesday, May 3, 2017 8:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] 1702 - Software Center settings and notification messages for 
high-impact task sequences

I recently upgraded from 1602 > 1702 without issue. I want to take advantage of 
the new notification messages during an OS upgrade task sequence but I can't 
seem to get it to work. I also don't seem to be able to get the custom Software 
Center properties to show up for the new task sequence either.

Here are the steps I took to test this - I created a new OS Upgrade task 
sequence and I modified the User Notification tab with custom text and made 
sure the check box was in this is a high impact task sequence. I then deployed 
the task sequence to a client expecting to see the custom Software center 
properties settings as well as the custom user notification text when I kicked 
off the task sequence. Instead I saw all of the default values in Software 
Center as well as the default notification text letting my users know they were 
going to lose all of their data and settings. :)

Here are the screenshots of my task sequence settings and what I see in 
Software Center.

[cid:image001.jpg@01D2C3EB.B347BE40]  [cid:image002.jpg@01D2C3EB.B347BE40]

[cid:image003.jpg@01D2C3EB.B347BE40]   [cid:image004.png@01D2C3EB.B347BE40]



Any idea where I should start troubleshooting this issue?






[mssms] RE: 1702 - Software Center settings and notification messages for high-impact task sequences

2017-05-03 Thread Enley, Carl
Actually it was a brand new task sequence, but yes I do the same thing as you. 
I change the title slightly and then force a sync and verify that I see the 
change in software center.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Melin, Cordell (BAC/LAC)
Sent: Wednesday, May 3, 2017 9:10 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: 1702 - Software Center settings and notification messages 
for high-impact task sequences

Small thing, but could it be that your Software Center was not updated with the 
latest information on your task sequence deployment?

During testing, I usually add a number or letter to the end of the Task 
Sequence name so that when I go to the Software Center I am sure I have the 
latest changes.

Cordell

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl
Sent: May 3, 2017 8:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] 1702 - Software Center settings and notification messages for 
high-impact task sequences

I recently upgraded from 1602 > 1702 without issue. I want to take advantage of 
the new notification messages during an OS upgrade task sequence but I can't 
seem to get it to work. I also don't seem to be able to get the custom Software 
Center properties to show up for the new task sequence either.

Here are the steps I took to test this - I created a new OS Upgrade task 
sequence and I modified the User Notification tab with custom text and made 
sure the check box was in this is a high impact task sequence. I then deployed 
the task sequence to a client expecting to see the custom Software center 
properties settings as well as the custom user notification text when I kicked 
off the task sequence. Instead I saw all of the default values in Software 
Center as well as the default notification text letting my users know they were 
going to lose all of their data and settings. :)

Here are the screenshots of my task sequence settings and what I see in 
Software Center.

[cid:image001.jpg@01D2C3EF.284B76C0]  [cid:image002.jpg@01D2C3EF.284B76C0]

[cid:image003.jpg@01D2C3EF.284B76C0]   [cid:image004.png@01D2C3EF.284B76C0]



Any idea where I should start troubleshooting this issue?







[mssms] RE: 1702 - Software Center settings and notification messages for high-impact task sequences

2017-05-03 Thread Melin, Cordell (BAC/LAC)
Small thing, but could it be that your Software Center was not updated with the 
latest information on your task sequence deployment?

During testing, I usually add a number or letter to the end of the Task 
Sequence name so that when I go to the Software Center I am sure I have the 
latest changes.

Cordell

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Enley, Carl
Sent: May 3, 2017 8:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] 1702 - Software Center settings and notification messages for 
high-impact task sequences

I recently upgraded from 1602 > 1702 without issue. I want to take advantage of 
the new notification messages during an OS upgrade task sequence but I can't 
seem to get it to work. I also don't seem to be able to get the custom Software 
Center properties to show up for the new task sequence either.

Here are the steps I took to test this - I created a new OS Upgrade task 
sequence and I modified the User Notification tab with custom text and made 
sure the check box was in this is a high impact task sequence. I then deployed 
the task sequence to a client expecting to see the custom Software center 
properties settings as well as the custom user notification text when I kicked 
off the task sequence. Instead I saw all of the default values in Software 
Center as well as the default notification text letting my users know they were 
going to lose all of their data and settings. :)

Here are the screenshots of my task sequence settings and what I see in 
Software Center.

[cid:image001.jpg@01D2C3ED.1924BFF0]  [cid:image002.jpg@01D2C3ED.1924BFF0]

[cid:image003.jpg@01D2C3ED.1924BFF0]   [cid:image004.png@01D2C3ED.1924BFF0]



Any idea where I should start troubleshooting this issue?






[mssms] 1702 - Software Center settings and notification messages for high-impact task sequences

2017-05-03 Thread Enley, Carl
I recently upgraded from 1602 > 1702 without issue. I want to take advantage of 
the new notification messages during an OS upgrade task sequence but I can't 
seem to get it to work. I also don't seem to be able to get the custom Software 
Center properties to show up for the new task sequence either.

Here are the steps I took to test this - I created a new OS Upgrade task 
sequence and I modified the User Notification tab with custom text and made 
sure the check box was in this is a high impact task sequence. I then deployed 
the task sequence to a client expecting to see the custom Software center 
properties settings as well as the custom user notification text when I kicked 
off the task sequence. Instead I saw all of the default values in Software 
Center as well as the default notification text letting my users know they were 
going to lose all of their data and settings. :)

Here are the screenshots of my task sequence settings and what I see in 
Software Center.

[cid:image003.jpg@01D2C3E9.BCF736C0]  [cid:image005.jpg@01D2C3E9.BCF736C0]

[cid:image008.jpg@01D2C3E9.BCF736C0]   [cid:image010.png@01D2C3E9.614A47E0]



Any idea where I should start troubleshooting this issue?