vista nda s what s ok what s not

Right, let's get this one clear again. I *URGE* everyone to read this, no matter how boring it is - I'm cross posting this to a couple of newsgroups just to be sure.
Microsoft internal builds are protected by employee contracts. This doesn't just apply to Vista, it applies to absolutely every product there is. Internal builds are directly not allowed to be distributed to anyone outside their particular product group.
Builds that have been pushed to a select group of technical testers cannot be distributed either to *non-technical testers*. It's been made clear to me by an employee, that if you burn a DVD with Vista on for example who has the ability to download the build but cannot (due to bandwidth or bad connection etc.) *can* be distributed to them, but if you email the given alias on the Connect site and ask them first, they're probably not going to say no to it.
Technical testers who have access to Connect and the beta stuff, cannot distribute *anything from Connect*. Once you sign in and have access to the beta material, that point on anything you see or have access to *cannot* be distributed to anyone else.
MSDN and TechNet - read through the terms and conditions either on the respective websites and you'll find pretty much the same thing. You *can* however, blog about Vista, post screenshots, post tips and hints, post reviews and general information that is *not* from Connect, anywhere in the public domain.
Sites such as Neowin, JCXP, Winsupersite, and even our group blog MSBLOG, they have to be taken with a pinch of salt unless there is a direct source to a blog or posting which has the prefix http://blogs.technet.com, http://blogs.msdn.com, http://blogs.microsoft.com, http://www.microsoft.com or http://www.msdn.com, as these are posted by Microsoft employees and therefore add more of a genuine element to the story or article itself.
I really hope this is clear for everyone, especially Kevin who repeatidly posts complete rubbish such as the previous post to this.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :--

Take off this line to be more accurate "unless there is a direct source to a blog or posting which has the prefix..." Blogs are not official sources of information even if posted by Microsoft employees on Microsoft servers. Blogs are the employees writing and opinion and little more since there is no oversight as there is on the Microsoft.com website. The checks and balance on the website do not exist on blogs except errors on blogs are corrected after they are posted as they are recognized. Because of that, there is more chance for errors on a blog and in fact errors are seen on Microsoft blogs occasionally.
-- Jupiter Jones [MVP] http://www3.telus.net/dandemar http://www.dts-l.org
"Zack Whittaker" wrote in message

Right, let's get this one clear again. I *URGE* everyone to read this, no matter how boring it is - I'm cross posting this to a couple of newsgroups just to be sure.
Microsoft internal builds are protected by employee contracts. This doesn't just apply to Vista, it applies to absolutely every product there is. Internal builds are directly not allowed to be distributed to anyone outside their particular product group.
Builds that have been pushed to a select group of technical testers cannot be distributed either to *non-technical testers*. It's been made clear to me by an employee, that if you burn a DVD with Vista on for example who has the ability to download the build but cannot (due to bandwidth or bad connection etc.) *can* be distributed to them, but if you email the given alias on the Connect site and ask them first, they're probably not going to say no to it.
Technical testers who have access to Connect and the beta stuff, cannot distribute *anything from Connect*. Once you sign in and have access to the beta material, that point on anything you see or have access to *cannot* be distributed to anyone else.
MSDN and TechNet - read through the terms and conditions either on the respective websites and you'll find pretty much the same thing. You *can* however, blog about Vista, post screenshots, post tips and hints, post reviews and general information that is *not* from Connect, anywhere in the public domain.
Sites such as Neowin, JCXP, Winsupersite, and even our group blog MSBLOG, they have to be taken with a pinch of salt unless there is a direct source to a blog or posting which has the prefix http://blogs.technet.com, http://blogs.msdn.com, http://blogs.microsoft.com, http://www.microsoft.com or http://www.msdn.com, as these are posted by Microsoft employees and therefore add more of a genuine element to the story or article itself.
I really hope this is clear for everyone, especially Kevin who repeatidly posts complete rubbish such as the previous post to this.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :--

"Zack Whittaker" wrote in message

Right, let's get this one clear again. I *URGE* everyone to read this, no matter how boring it is - I'm cross posting this to a couple of newsgroups just to be sure.
Microsoft internal builds are protected by employee contracts. This doesn't just apply to Vista, it applies to absolutely every product there is. Internal builds are directly not allowed to be distributed to anyone outside their particular product group.
Builds that have been pushed to a select group of technical testers cannot be distributed either to *non-technical testers*. It's been made clear to me by an employee, that if you burn a DVD with Vista on for example who has the ability to download the build but cannot (due to bandwidth or bad connection etc.) *can* be distributed to them, but if you email the given alias on the Connect site and ask them first, they're probably not going to say no to it.
Technical testers who have access to Connect and the beta stuff, cannot distribute *anything from Connect*. Once you sign in and have access to the beta material, that point on anything you see or have access to *cannot* be distributed to anyone else.
MSDN and TechNet - read through the terms and conditions either on the respective websites and you'll find pretty much the same thing. You *can* however, blog about Vista, post screenshots, post tips and hints, post reviews and general information that is *not* from Connect, anywhere in the public domain.
Sites such as Neowin, JCXP, Winsupersite, and even our group blog MSBLOG, they have to be taken with a pinch of salt unless there is a direct source to a blog or posting which has the prefix http://blogs.technet.com, http://blogs.msdn.com, http://blogs.microsoft.com, http://www.microsoft.com or http://www.msdn.com, as these are posted by Microsoft employees and therefore add more of a genuine element to the story or article itself.
I really hope this is clear for everyone, especially Kevin who repeatidly posts complete rubbish such as the previous post to this.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :--

Clear up one thing for me though,please . My MSDN liscence says I can install Operating systems (I guess VISTA included on up to 10 pcs) as per the agreement I signed electronically and on the pages where I download Vista and other Operating Systems. Ok does what you just said limit me to just one machine with vista or does the MSDN liscence still apply?

Your MSDN takes presedence over it. I can have 10/15 Vista installs on my TechNet Plus, so that takes presedence for me if I install a TechNet build.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :-- "michael e dziatkowicz" wrote in message

"Zack Whittaker" wrote in message Right, let's get this one clear again. I *URGE* everyone to read this, no matter how boring it is - I'm cross posting this to a couple of newsgroups just to be sure.
Microsoft internal builds are protected by employee contracts. This doesn't just apply to Vista, it applies to absolutely every product there is. Internal builds are directly not allowed to be distributed to anyone outside their particular product group.
Builds that have been pushed to a select group of technical testers cannot be distributed either to *non-technical testers*. It's been made clear to me by an employee, that if you burn a DVD with Vista on for example who has the ability to download the build but cannot (due to bandwidth or bad connection etc.) *can* be distributed to them, but if you email the given alias on the Connect site and ask them first, they're probably not going to say no to it.
Technical testers who have access to Connect and the beta stuff, cannot distribute *anything from Connect*. Once you sign in and have access to the beta material, that point on anything you see or have access to *cannot* be distributed to anyone else.
MSDN and TechNet - read through the terms and conditions either on the respective websites and you'll find pretty much the same thing. You *can* however, blog about Vista, post screenshots, post tips and hints, post reviews and general information that is *not* from Connect, anywhere in the public domain.
Sites such as Neowin, JCXP, Winsupersite, and even our group blog MSBLOG, they have to be taken with a pinch of salt unless there is a direct source to a blog or posting which has the prefix http://blogs.technet.com, http://blogs.msdn.com, http://blogs.microsoft.com, http://www.microsoft.com or http://www.msdn.com, as these are posted by Microsoft employees and therefore add more of a genuine element to the story or article itself.
I really hope this is clear for everyone, especially Kevin who repeatidly posts complete rubbish such as the previous post to this.
-- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up!
--: Original message follows :--
Clear up one thing for me though,please . My MSDN liscence says I can install Operating systems (I guess VISTA included on up to 10 pcs) as per the agreement I signed electronically and on the pages where I download Vista and other Operating Systems. Ok does what you just said limit me to just one machine with vista or does the MSDN liscence still apply?

Zack Whittaker wrote:

Right, let's get this one clear again. I *URGE* everyone to read this, no matter how boring it is - I'm cross posting this to a couple of newsgroups just to be sure.

I think the only person this is not clear for is Kevin, and it wouldn't matter if Bill Gates descended from heaven into his bedroom with a choir of angels telling him otherwise.