WSUS 3 - showing computers but only one at a time

  • Thread starter Thread starter Ehren
  • Start date Start date
E

Ehren

Hello-

I have a very strange issue that I have never seen before and wonder if
anyone else has any experience with it.

We have several computer labs here, each with 10-12 computers. We have a
main domain, call it "maindomain" and then we have a separate domain for the
labs ... call it "teaching". The WSUS server is in the maindomain and
obviously the lab computers are in the teaching domain. In my head this
shouldnt be an issue because you just configure the computers via group
policy to point to the wsus server and it really doesnt matter what domain
its in because its http (right?).

To save myself dns hasstles I configured automatic updates via group policy
for this lab in the teaching domain, setting the update location to be
http://<ipaddress_of_WSUS_server>. The WSUS server update site is configured
as the default site on port 80.

All of the computers in the lab have recieved updates from the WSUS server
and have installed them automatically as they should (i know this because
thier ip range does not have internet access so if not for the wsus server
its impossible to download updates). Last night at the scheduled time they
all rebooted and installed 12 updates that they had scheduled.

heres the interesting part...10 of the computers are all dell Optiplex
GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11) ALWAYS shows
up in the update services console. However bps1263-xx (where xx=1-10) show
up in the console, but no more than one at a time. I.e. bps1263-00 will
show up for a while, then that will be gone and bps1263-07 will show up, then
that will be gone and bps1263-04 will show up and on and on.

All of these computers were imaged using sysprep. So although they all use
the same image they all have unique sid's and the like because they all went
through the mini-windows welcome setup after they were imaged.

Any ideas here? This is blowing my mind! :)

TIA - Ehren
 
As a note they are all configured to use a proxy...however they are
configured to not use the proxy server for local (intranet) addresses.
Figured I would note that even though I feel it is irrelevent since this is a
local address we are dealing with.

"Ehren" wrote:

> Hello-
>
> I have a very strange issue that I have never seen before and wonder if
> anyone else has any experience with it.
>
> We have several computer labs here, each with 10-12 computers. We have a
> main domain, call it "maindomain" and then we have a separate domain for the
> labs ... call it "teaching". The WSUS server is in the maindomain and
> obviously the lab computers are in the teaching domain. In my head this
> shouldnt be an issue because you just configure the computers via group
> policy to point to the wsus server and it really doesnt matter what domain
> its in because its http (right?).
>
> To save myself dns hasstles I configured automatic updates via group policy
> for this lab in the teaching domain, setting the update location to be
> http://<ipaddress_of_WSUS_server>. The WSUS server update site is configured
> as the default site on port 80.
>
> All of the computers in the lab have recieved updates from the WSUS server
> and have installed them automatically as they should (i know this because
> thier ip range does not have internet access so if not for the wsus server
> its impossible to download updates). Last night at the scheduled time they
> all rebooted and installed 12 updates that they had scheduled.
>
> heres the interesting part...10 of the computers are all dell Optiplex
> GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11) ALWAYS shows
> up in the update services console. However bps1263-xx (where xx=1-10) show
> up in the console, but no more than one at a time. I.e. bps1263-00 will
> show up for a while, then that will be gone and bps1263-07 will show up, then
> that will be gone and bps1263-04 will show up and on and on.
>
> All of these computers were imaged using sysprep. So although they all use
> the same image they all have unique sid's and the like because they all went
> through the mini-windows welcome setup after they were imaged.
>
> Any ideas here? This is blowing my mind! :)
>
> TIA - Ehren
 
What going on is that the WSUS ID is not unique ... is created when the PC
is first connected to WSUS and not there after. So if your master imahe had
a WSUS ID now all your image created PC's have the same ones. For WSUS 2 the
fix is as follows:
use regedit and go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
delete the following entries
"PingID"
"AccountDomainSid"
"SusClientId"
then retart the two services /restart PC
For good measure you can also run wuauclt.exe /resetauthorization /detectnow
in the command console

This can be scripted and various scripts can be found on line

http://www.wsus.info/forums/lofiversion/index.php?t8698.html

run it as a start up script and it will fix stuf. This is how we do it.


"Ehren" <Ehren@discussions.microsoft.com> wrote in message
news:AB820213-454C-4392-9EB5-BB76B88703E7@microsoft.com...
> Hello-
>
> I have a very strange issue that I have never seen before and wonder if
> anyone else has any experience with it.
>
> We have several computer labs here, each with 10-12 computers. We have a
> main domain, call it "maindomain" and then we have a separate domain for
> the
> labs ... call it "teaching". The WSUS server is in the maindomain and
> obviously the lab computers are in the teaching domain. In my head this
> shouldnt be an issue because you just configure the computers via group
> policy to point to the wsus server and it really doesnt matter what domain
> its in because its http (right?).
>
> To save myself dns hasstles I configured automatic updates via group
> policy
> for this lab in the teaching domain, setting the update location to be
> http://<ipaddress_of_WSUS_server>. The WSUS server update site is
> configured
> as the default site on port 80.
>
> All of the computers in the lab have recieved updates from the WSUS server
> and have installed them automatically as they should (i know this because
> thier ip range does not have internet access so if not for the wsus server
> its impossible to download updates). Last night at the scheduled time
> they
> all rebooted and installed 12 updates that they had scheduled.
>
> heres the interesting part...10 of the computers are all dell Optiplex
> GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11) ALWAYS
> shows
> up in the update services console. However bps1263-xx (where xx=1-10)
> show
> up in the console, but no more than one at a time. I.e. bps1263-00 will
> show up for a while, then that will be gone and bps1263-07 will show up,
> then
> that will be gone and bps1263-04 will show up and on and on.
>
> All of these computers were imaged using sysprep. So although they all
> use
> the same image they all have unique sid's and the like because they all
> went
> through the mini-windows welcome setup after they were imaged.
>
> Any ideas here? This is blowing my mind! :)
>
> TIA - Ehren
 
I have WSUS 3 but maybe its the same

what file extension would that script have when saved?

Thanks

"WorkingHard" wrote:

> What going on is that the WSUS ID is not unique ... is created when the PC
> is first connected to WSUS and not there after. So if your master imahe had
> a WSUS ID now all your image created PC's have the same ones. For WSUS 2 the
> fix is as follows:
> use regedit and go to
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
> delete the following entries
> "PingID"
> "AccountDomainSid"
> "SusClientId"
> then retart the two services /restart PC
> For good measure you can also run wuauclt.exe /resetauthorization /detectnow
> in the command console
>
> This can be scripted and various scripts can be found on line
>
> http://www.wsus.info/forums/lofiversion/index.php?t8698.html
>
> run it as a start up script and it will fix stuf. This is how we do it.
>
>
> "Ehren" <Ehren@discussions.microsoft.com> wrote in message
> news:AB820213-454C-4392-9EB5-BB76B88703E7@microsoft.com...
> > Hello-
> >
> > I have a very strange issue that I have never seen before and wonder if
> > anyone else has any experience with it.
> >
> > We have several computer labs here, each with 10-12 computers. We have a
> > main domain, call it "maindomain" and then we have a separate domain for
> > the
> > labs ... call it "teaching". The WSUS server is in the maindomain and
> > obviously the lab computers are in the teaching domain. In my head this
> > shouldnt be an issue because you just configure the computers via group
> > policy to point to the wsus server and it really doesnt matter what domain
> > its in because its http (right?).
> >
> > To save myself dns hasstles I configured automatic updates via group
> > policy
> > for this lab in the teaching domain, setting the update location to be
> > http://<ipaddress_of_WSUS_server>. The WSUS server update site is
> > configured
> > as the default site on port 80.
> >
> > All of the computers in the lab have recieved updates from the WSUS server
> > and have installed them automatically as they should (i know this because
> > thier ip range does not have internet access so if not for the wsus server
> > its impossible to download updates). Last night at the scheduled time
> > they
> > all rebooted and installed 12 updates that they had scheduled.
> >
> > heres the interesting part...10 of the computers are all dell Optiplex
> > GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11) ALWAYS
> > shows
> > up in the update services console. However bps1263-xx (where xx=1-10)
> > show
> > up in the console, but no more than one at a time. I.e. bps1263-00 will
> > show up for a while, then that will be gone and bps1263-07 will show up,
> > then
> > that will be gone and bps1263-04 will show up and on and on.
> >
> > All of these computers were imaged using sysprep. So although they all
> > use
> > the same image they all have unique sid's and the like because they all
> > went
> > through the mini-windows welcome setup after they were imaged.
> >
> > Any ideas here? This is blowing my mind! :)
> >
> > TIA - Ehren
>
>
>
 
it's vbs Visual Basic script

Just check the registry I can't get to a WSUS 3 client right now to look
myself.


"Ehren" <Ehren@discussions.microsoft.com> wrote in message
news:8E0E5EAA-1436-47E2-A629-97DEE646D40F@microsoft.com...
>I have WSUS 3 but maybe its the same
>
> what file extension would that script have when saved?
>
> Thanks
>
> "WorkingHard" wrote:
>
>> What going on is that the WSUS ID is not unique ... is created when the
>> PC
>> is first connected to WSUS and not there after. So if your master imahe
>> had
>> a WSUS ID now all your image created PC's have the same ones. For WSUS 2
>> the
>> fix is as follows:
>> use regedit and go to
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
>> delete the following entries
>> "PingID"
>> "AccountDomainSid"
>> "SusClientId"
>> then retart the two services /restart PC
>> For good measure you can also run wuauclt.exe /resetauthorization
>> /detectnow
>> in the command console
>>
>> This can be scripted and various scripts can be found on line
>>
>> http://www.wsus.info/forums/lofiversion/index.php?t8698.html
>>
>> run it as a start up script and it will fix stuf. This is how we do it.
>>
>>
>> "Ehren" <Ehren@discussions.microsoft.com> wrote in message
>> news:AB820213-454C-4392-9EB5-BB76B88703E7@microsoft.com...
>> > Hello-
>> >
>> > I have a very strange issue that I have never seen before and wonder if
>> > anyone else has any experience with it.
>> >
>> > We have several computer labs here, each with 10-12 computers. We have
>> > a
>> > main domain, call it "maindomain" and then we have a separate domain
>> > for
>> > the
>> > labs ... call it "teaching". The WSUS server is in the maindomain and
>> > obviously the lab computers are in the teaching domain. In my head
>> > this
>> > shouldnt be an issue because you just configure the computers via group
>> > policy to point to the wsus server and it really doesnt matter what
>> > domain
>> > its in because its http (right?).
>> >
>> > To save myself dns hasstles I configured automatic updates via group
>> > policy
>> > for this lab in the teaching domain, setting the update location to be
>> > http://<ipaddress_of_WSUS_server>. The WSUS server update site is
>> > configured
>> > as the default site on port 80.
>> >
>> > All of the computers in the lab have recieved updates from the WSUS
>> > server
>> > and have installed them automatically as they should (i know this
>> > because
>> > thier ip range does not have internet access so if not for the wsus
>> > server
>> > its impossible to download updates). Last night at the scheduled time
>> > they
>> > all rebooted and installed 12 updates that they had scheduled.
>> >
>> > heres the interesting part...10 of the computers are all dell Optiplex
>> > GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11) ALWAYS
>> > shows
>> > up in the update services console. However bps1263-xx (where xx=1-10)
>> > show
>> > up in the console, but no more than one at a time. I.e. bps1263-00
>> > will
>> > show up for a while, then that will be gone and bps1263-07 will show
>> > up,
>> > then
>> > that will be gone and bps1263-04 will show up and on and on.
>> >
>> > All of these computers were imaged using sysprep. So although they all
>> > use
>> > the same image they all have unique sid's and the like because they all
>> > went
>> > through the mini-windows welcome setup after they were imaged.
>> >
>> > Any ideas here? This is blowing my mind! :)
>> >
>> > TIA - Ehren
>>
>>
>>
 
They only key that was there was the susid one, and they were all the same.
So i deleted them and we will see if they all check in by the morning. I
will post back when I know. Thanks

"WorkingHard" wrote:

> it's vbs Visual Basic script
>
> Just check the registry I can't get to a WSUS 3 client right now to look
> myself.
>
>
> "Ehren" <Ehren@discussions.microsoft.com> wrote in message
> news:8E0E5EAA-1436-47E2-A629-97DEE646D40F@microsoft.com...
> >I have WSUS 3 but maybe its the same
> >
> > what file extension would that script have when saved?
> >
> > Thanks
> >
> > "WorkingHard" wrote:
> >
> >> What going on is that the WSUS ID is not unique ... is created when the
> >> PC
> >> is first connected to WSUS and not there after. So if your master imahe
> >> had
> >> a WSUS ID now all your image created PC's have the same ones. For WSUS 2
> >> the
> >> fix is as follows:
> >> use regedit and go to
> >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
> >> delete the following entries
> >> "PingID"
> >> "AccountDomainSid"
> >> "SusClientId"
> >> then retart the two services /restart PC
> >> For good measure you can also run wuauclt.exe /resetauthorization
> >> /detectnow
> >> in the command console
> >>
> >> This can be scripted and various scripts can be found on line
> >>
> >> http://www.wsus.info/forums/lofiversion/index.php?t8698.html
> >>
> >> run it as a start up script and it will fix stuf. This is how we do it.
> >>
> >>
> >> "Ehren" <Ehren@discussions.microsoft.com> wrote in message
> >> news:AB820213-454C-4392-9EB5-BB76B88703E7@microsoft.com...
> >> > Hello-
> >> >
> >> > I have a very strange issue that I have never seen before and wonder if
> >> > anyone else has any experience with it.
> >> >
> >> > We have several computer labs here, each with 10-12 computers. We have
> >> > a
> >> > main domain, call it "maindomain" and then we have a separate domain
> >> > for
> >> > the
> >> > labs ... call it "teaching". The WSUS server is in the maindomain and
> >> > obviously the lab computers are in the teaching domain. In my head
> >> > this
> >> > shouldnt be an issue because you just configure the computers via group
> >> > policy to point to the wsus server and it really doesnt matter what
> >> > domain
> >> > its in because its http (right?).
> >> >
> >> > To save myself dns hasstles I configured automatic updates via group
> >> > policy
> >> > for this lab in the teaching domain, setting the update location to be
> >> > http://<ipaddress_of_WSUS_server>. The WSUS server update site is
> >> > configured
> >> > as the default site on port 80.
> >> >
> >> > All of the computers in the lab have recieved updates from the WSUS
> >> > server
> >> > and have installed them automatically as they should (i know this
> >> > because
> >> > thier ip range does not have internet access so if not for the wsus
> >> > server
> >> > its impossible to download updates). Last night at the scheduled time
> >> > they
> >> > all rebooted and installed 12 updates that they had scheduled.
> >> >
> >> > heres the interesting part...10 of the computers are all dell Optiplex
> >> > GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11) ALWAYS
> >> > shows
> >> > up in the update services console. However bps1263-xx (where xx=1-10)
> >> > show
> >> > up in the console, but no more than one at a time. I.e. bps1263-00
> >> > will
> >> > show up for a while, then that will be gone and bps1263-07 will show
> >> > up,
> >> > then
> >> > that will be gone and bps1263-04 will show up and on and on.
> >> >
> >> > All of these computers were imaged using sysprep. So although they all
> >> > use
> >> > the same image they all have unique sid's and the like because they all
> >> > went
> >> > through the mini-windows welcome setup after they were imaged.
> >> >
> >> > Any ideas here? This is blowing my mind! :)
> >> >
> >> > TIA - Ehren
> >>
> >>
> >>
>
>
>
 
Kind of normal. When you delete those keys that's the only one that returns.
The other ones might be remainders of WSUS 1 or so. I'm not sure.
"Ehren" <Ehren@discussions.microsoft.com> wrote in message
news:021148E8-A913-4D85-B64E-328F7F721718@microsoft.com...
> They only key that was there was the susid one, and they were all the
> same.
> So i deleted them and we will see if they all check in by the morning. I
> will post back when I know. Thanks
>
> "WorkingHard" wrote:
>
>> it's vbs Visual Basic script
>>
>> Just check the registry I can't get to a WSUS 3 client right now to look
>> myself.
>>
>>
>> "Ehren" <Ehren@discussions.microsoft.com> wrote in message
>> news:8E0E5EAA-1436-47E2-A629-97DEE646D40F@microsoft.com...
>> >I have WSUS 3 but maybe its the same
>> >
>> > what file extension would that script have when saved?
>> >
>> > Thanks
>> >
>> > "WorkingHard" wrote:
>> >
>> >> What going on is that the WSUS ID is not unique ... is created when
>> >> the
>> >> PC
>> >> is first connected to WSUS and not there after. So if your master
>> >> imahe
>> >> had
>> >> a WSUS ID now all your image created PC's have the same ones. For WSUS
>> >> 2
>> >> the
>> >> fix is as follows:
>> >> use regedit and go to
>> >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
>> >> delete the following entries
>> >> "PingID"
>> >> "AccountDomainSid"
>> >> "SusClientId"
>> >> then retart the two services /restart PC
>> >> For good measure you can also run wuauclt.exe /resetauthorization
>> >> /detectnow
>> >> in the command console
>> >>
>> >> This can be scripted and various scripts can be found on line
>> >>
>> >> http://www.wsus.info/forums/lofiversion/index.php?t8698.html
>> >>
>> >> run it as a start up script and it will fix stuf. This is how we do
>> >> it.
>> >>
>> >>
>> >> "Ehren" <Ehren@discussions.microsoft.com> wrote in message
>> >> news:AB820213-454C-4392-9EB5-BB76B88703E7@microsoft.com...
>> >> > Hello-
>> >> >
>> >> > I have a very strange issue that I have never seen before and wonder
>> >> > if
>> >> > anyone else has any experience with it.
>> >> >
>> >> > We have several computer labs here, each with 10-12 computers. We
>> >> > have
>> >> > a
>> >> > main domain, call it "maindomain" and then we have a separate domain
>> >> > for
>> >> > the
>> >> > labs ... call it "teaching". The WSUS server is in the maindomain
>> >> > and
>> >> > obviously the lab computers are in the teaching domain. In my head
>> >> > this
>> >> > shouldnt be an issue because you just configure the computers via
>> >> > group
>> >> > policy to point to the wsus server and it really doesnt matter what
>> >> > domain
>> >> > its in because its http (right?).
>> >> >
>> >> > To save myself dns hasstles I configured automatic updates via group
>> >> > policy
>> >> > for this lab in the teaching domain, setting the update location to
>> >> > be
>> >> > http://<ipaddress_of_WSUS_server>. The WSUS server update site is
>> >> > configured
>> >> > as the default site on port 80.
>> >> >
>> >> > All of the computers in the lab have recieved updates from the WSUS
>> >> > server
>> >> > and have installed them automatically as they should (i know this
>> >> > because
>> >> > thier ip range does not have internet access so if not for the wsus
>> >> > server
>> >> > its impossible to download updates). Last night at the scheduled
>> >> > time
>> >> > they
>> >> > all rebooted and installed 12 updates that they had scheduled.
>> >> >
>> >> > heres the interesting part...10 of the computers are all dell
>> >> > Optiplex
>> >> > GX280's and one is a Dell Optiplex 170L. The 170L (bps1263-11)
>> >> > ALWAYS
>> >> > shows
>> >> > up in the update services console. However bps1263-xx (where
>> >> > xx=1-10)
>> >> > show
>> >> > up in the console, but no more than one at a time. I.e. bps1263-00
>> >> > will
>> >> > show up for a while, then that will be gone and bps1263-07 will show
>> >> > up,
>> >> > then
>> >> > that will be gone and bps1263-04 will show up and on and on.
>> >> >
>> >> > All of these computers were imaged using sysprep. So although they
>> >> > all
>> >> > use
>> >> > the same image they all have unique sid's and the like because they
>> >> > all
>> >> > went
>> >> > through the mini-windows welcome setup after they were imaged.
>> >> >
>> >> > Any ideas here? This is blowing my mind! :)
>> >> >
>> >> > TIA - Ehren
>> >>
>> >>
>> >>
>>
>>
>>
 

Similar threads

AWS
Skilling snack: Windows monthly updates
Replies
0
Views
155
AWS
AWS
AWS
Windows monthly updates explained
Replies
0
Views
132
AWS
AWS
AWS
Get the most out of expedited Windows quality updates
Replies
0
Views
168
AWS
AWS
AWS
Malware Scanning for cloud storage GA pre-announcement | prevent malicious content distribution
Replies
0
Views
97
AWS
AWS
AWS
Microsoft 365 Admin Monthly Digest – April 2023
Replies
0
Views
129
AWS
AWS
Back
Top