That is, indeed, some wonkiness. There's no RBA that would impact the account logging into the console, is there?
You may want to open up a ticket with MSFT to make sure things are healthy.... On Thu, Jul 28, 2016 at 2:21 PM, Chris Carbone < [email protected]> wrote: > Not silly at all, I am willing to look at anything. The client is > installed, I have a couple of the computers in my office that should be > appearing but do not. Plus there are other deployments to these machines > where this is not an issue. None of this makes any sense. :D > > > > Just to add more confusion. The application that I’m deploying does show > up in Software Center and if I install it, THEN it will show up under the > status for that deployment. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Thursday, July 28, 2016 2:06 PM > *To:* [email protected] > *Subject:* Re: [mssms] FW: Strange issue with deployments > > > > Silly question, but is the client installed on the ones that do not show > up? You could have added records where the client is not installed. You > would see them in the collection, but not in status messages, because they > are not clients. > > In the collection view see if the client = yes and active = yes. > > > > I have a new collection with 31 members and if I go into that collection > I see them all. > > When I check under deployment status for that software it shows success > for 1/1 and that is it, the other 30 machines do not appear under any other > category. > > > > On Thu, Jul 28, 2016 at 11:10 AM, Chris Carbone < > [email protected]> wrote: > > Yes, these exist in the limiting “All Workstations” collection. But just > for the heck of it I just ran the update membership option. > > > > As for SQL query against the DB go, I do not have access to this which > also means I cannot use ceviewer tool. I will try again to see if I can > gain access to the db. Would sure help! J > > > > Thanks for the suggestions. I already viewed the Colleval.log and nothing > stuck out but I will look closer to see the logs generated from when these > new collections were built. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Adam Juelich > *Sent:* Thursday, July 28, 2016 10:51 AM > *To:* [email protected] > *Subject:* Re: [mssms] FW: Strange issue with deployments > > > > Do they exist within the 'Limiting Collection?' Update membership of > limiting collection and browse it to see if those Devices/Users exist > within it. > > > > On Thu, Jul 28, 2016 at 10:26 AM, Chris Carbone < > [email protected]> wrote: > > All of these members are direct. I went into devices, found each computer, > right clicked and added to collection. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Adam Juelich > *Sent:* Thursday, July 28, 2016 9:23 AM > *To:* [email protected] > *Subject:* Re: [mssms] FW: Strange issue with deployments > > > > Are the members of the Collection in there from a Direct Query, or > otherwise? > > > > On Thu, Jul 28, 2016 at 9:00 AM, Chris Carbone < > [email protected]> wrote: > > Nobody else has ever heard of this issue before? We are currently on 1511 > and I have a few deployments that are like this now where under deployment > status most of the computers in that collection are not appearing. Yet if I > go into that collection the computers do appear. > > > > *From:* Chris Carbone > *Sent:* Monday, July 25, 2016 8:45 AM > *To:* [email protected] > *Subject:* Strange issue with deployments > > > > Hello all, > > > > In the last week or so I have noticed now some new deployments are not > seeing all the members in a collection. For example I have a new collection > with 31 members and if I go into that collection I see them all. When I > check under deployment status for that software it shows success for 1/1 > and that is it, the other 30 machines do not appear under any other > category. > > > > I tried recreating the collection and also the deployment. We did make a > change with system discovery to only look at 1am each night for another > issue but don’t think this change is related to this new problem. > > > > Anyone else seen this type of behavior and know where I can look? I > searched and have not really seen any results coming up for this problem. > > > > Thanks in advance > > Chris > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > > > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > > > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > >
