Because for 2 reasons, first when the technicians who manage and class by operating system in WSUS console they don't know Windows 6.3 ?! (XP, 7, 8, 2003, 2008, 2008R2, 2012, 6.3 hu ??)
Then perhaps they should learn this!?
- Windows 3.1/95/98 = Windows 3.x
- Windows NT 4.0 = Windows 4.0
- Windows 2000 = Windows 5.0
- Windows XP = Windows 5.1
- Windows Server 2003 = Windows 5.2
- Windows Vista/Server 2008 = Windows 6.0
- Windows 7/Server 2008 R2 = Windows 6.1
- Windows 8/Server 2012 = Windows 6.2
- Windows 8.1/Server 2012 R2 = Windows 6.3
It ain't that hard.
Regardless, it doesn't affect the ability of the WUAgent to properly detect/report the state of the update; it doesn't affect the abilty to approve those updates for the group(s) containing the W8.1/WS2012R2 systems; and it doesn't affect the ability of
the WUAgent to download and install those updates. In short, this does NOT affect the ability to deploy patches whatsoever.
the second is that bug exist since the Windows 8.1 preview release in june 2013, What are Microsoft Doing (8 months...) for a minor bug ?
Doing exactly what they should. Treating it as a minor bug. Would it surprise you to know that there are "minor bugs" in Windows XP that have never been fixed!? There are "minor bugs" in Windows 7 that are never going to get fixed. There are "minor bugs"
in every piece of software on the globe that are never going to get fixed!
This bug don't exist with 2012 WSUS server...
Correct. WSUS v6.2 was properly coded to recognize W8/WS2012 systems; WSUS v6.3 has a bug and does not properly recognize W8.1/WS2012R2 systems. Nobody is denying that point.
Is very strange, i suppose Microsoft taken a very long time for oblige the clients to migrate from Windows 2008 to 2012 ?
I'm not really sure where this train of thought is coming from, but it really has nothing to do with this conversation.
Are you aware that there are WSUS Admins who still don't know there was an update released in May, 2012, that is a mandatory update for WSUS v3.2 and contains a mandatory upgrade for the Windows Update Agent? With so many people oblivious to CRITICAL updates
for the WSUS server, it's no doubt particularly difficult to get juiced up over yet-another update package, just to fix a string value that doesn't display the way you'd like it to. Hell it's not even incorrect, it's absolutely accurate! You just don't like
it, correct? But that's not the reason, it's just an observation of how absolutely trivial this complaint really is, IMNSHO.
Even a minor bug "a wide" Microsoft is not acceptable to wait 8 months and more...
Most of the global software development community would fundamentally disagree with this opinion. See my previous comments about the plethora of "minor bugs" in all of the software all over the globe that will never get fixed.
Especially without communication on this issue
Huh? There has been communication. I have posted in this thread, and a WSUS Program Manager has posted in another thread. The issue is a **COSMETIC** issue, which seems (for the moment) to be annoying only a very few people, and it will be fixed in the NEXT
PATCH PACKAGE for WSUS v3.2 -- whenever that becomes necessary and appropriate. Nobody has denied the bug exists; nobody has said it won't get fixed (in fact, it's been explicitly agreed that it will be fixed). The only thing that's not been stated is
when the fix will be released.
In the meantime, I would think you have more productive things to do than lose sleep and expend wasted typing effort over the trivial differences between the string "Windows 6.3" and "Windows Server 2012 R2". I know I certainly
do!
Other recent topics
