Msdn Subscription

/ Comments off



Microsoft Developer Network
Knowledge base
Available inEnglish
Successor(s)Microsoft Docs
OwnerMicrosoft
URLArchived official website at the Wayback Machine (archive index)
CommercialYes
RegistrationOptional
LaunchedSeptember 1992; 28 years ago
Current statusOffline

Microsoft Developer NetworkType of siteKnowledge baseAvailable inEnglishSuccessor (s)Microsoft DocsOwnerMicrosoftURLArchived official website at t. Visual Studio subscriptions come with different set of benefits depending on the subscription type and level. You have the option to buy just the Visual Studio IDE or to also get a comprehensive set of subscriber benefits that include cloud services, software for. Microsoft now offers MSDN subscriptions that correspond to all three versions of the forthcoming Visual Studio.NET. The new subscription levels became available this week. When will Visual Studio 2013 be available to download from MSDN for people with a subscription? I found the download page for it.

Microsoft Developer Network (MSDN) was the division of Microsoft responsible for managing the firm's relationship with developers and testers, such as hardware developers interested in the operating system (OS), and software developers developing on the various OS platforms or using the API or scripting languages of Microsoft's applications. The relationship management is situated in assorted media: web sites, newsletters, developer conferences, trade media, blogs and DVD distribution.[citation needed]

Starting in January 2020, the website is fully integrated with Microsoft Docs.[1]

Websites[]

MSDN's primary web presence at msdn.microsoft.com is a collection of sites for the developer community that provide information, documentation, and discussion that is authored both by Microsoft and by the community at large. Recently, Microsoft has placed emphasis on incorporation of forums, blogs, library annotations and social bookmarking to make MSDN an open dialog with the developer community rather than a one-way service.[2] The main website, and most of its constituent applications below are available in 56[3] or more languages.

Library[]

MSDN Library is a library of official technical documentation intended for independent developers of software for Microsoft Windows. MSDN Library documents the APIs that ship with Microsoft products and also includes sample code, technical articles, and other programming information. The library was freely available on the web, with CDs and DVDs of the most recent materials initially issued quarterly as part of an MSDN subscription. However, since 2006, they can be freely downloaded from Microsoft Download Center in the form of ISO images.[4][5][6]

Visual Studio Express ion integrates only with MSDN Express Library, which is a subset of the full MSDN Library, although either ion of the MSDN Library can be freely downloaded and installed standalone.

In Visual Studio 2010 MSDN Library is replaced with the new Help System, which is installed as a part of Visual Studio 2010 installation. Help Library Manager is used to install Help Content books covering selected topics.

In 2016, Microsoft introduced the new technical documentation platform, Microsoft Docs, intended as a replacement of TechNet and MSDN libraries.[7][8] Over the next two years, the content of MSDN Library was gradually migrated into Microsoft Docs.[9] Now most of MSDN Library pages redirect to the corresponding Microsoft Docs pages.[citation needed]

Integration with Visual Studio[]

Each ion of MSDN Library can only be accessed with one help viewer (Microsoft Document Explorer or other help viewer), which is integrated with the then current single version or sometimes two versions of Visual Studio. In addition, each new version of Visual Studio does not integrate with an earlier version of MSDN. A compatible MSDN Library is released with each new version of Visual Studio and included on Visual Studio DVD. As newer versions of Visual Studio are released, newer ions of MSDN Library do not integrate with older Visual Studio versions and do not even include old/obsolete documentation for deprecated or discontinued products. MSDN Library versions can be installed side-by-side, that is, both the older as well as the newer version of MSDN Library can co-exist.[citation needed]

Forums[]

MSDN Forums are the web-based forums used by the community to discuss a wide variety of software development topics. MSDN Forums were migrated to an all-new platform during 2008 that provided new features designed to improve efficiency such as inline preview of threads, AJAX filtering, and a slide-up post or.

Blogs[]

MSDN blogs is a series of blogs that were hosted under Microsoft's domainblogs.msdn.com. Some blogs are dedicated to a product – e.g. Visual Studio,[10]Internet Explorer,[11]PowerShell[12] – or a version of a product – e.g. Windows 7,[13]Windows 8[14] – while others belong to a Microsoft employee, e.g. Michael Howard[15] or Raymond Chen.[16]

In May 2020, the MSDN and TechNet blogs were closed and the content was archived at Microsoft Docs.[17]

Social bookmarking[]

Social bookmarking on MSDN Social was first launched in 2008, built on a new web platform that has user-tagging and feeds at its core. The goal of the social bookmarking application is to provide a method whereby members of the developer community can:

Subscription
  • Contribute to a database of quality links on any topic from across the web. By filtering on one or more tags, (e.g. '.net' and 'database') users can discover popular or recent links and subscribe to a feed of those links.
  • Find and follow experts' recommended sites. Each profile page includes a feed of the user's contributions. Users can be discovered through a drop-down menu on each bookmark.
  • Demonstrate their expertise through the links displayed in their profile.
  • Store their favorite links online.
Msdn

The initial release of the application provides standard features for the genre, including a bookmarklet and import capabilities. The MSDN web site is also starting to incorporate feeds of social bookmarks from experts and the community, displayed alongside feeds from relevant bloggers.[18]

Social Bookmarks was discontinued on October 1, 2009.

Gallery[]

MSDN Gallery is a repository of community-authored code samples and projects. Launched in 2008, the purpose of the site is still evolving to complement Codeplex, the open-source project hosting site from Microsoft.

Software subscriptions[]

MSDN has historically offered a subscription package whereby developers have access and licenses to use nearly all Microsoft software that has ever been released to the public. Subscriptions are sold on an annual basis, and cost anywhere from US$1,000 to US$6,000 per year per subscription, as it is offered in several tiers.

Although in most cases the software itself functions exactly like the full product, the MSDN end-user license agreement[19] prohibits use of the software in a business production environment. This is a legal restriction, not a technical one. An exception is made[19] for Microsoft Office, allowing personal use even for business purposes without a separate license—but only with the 'MSDN Premium Subscription' and even so only 'directly related to the design, development and test and/or documentation of software projects;' this does not terminate[20]

MSDN Magazine[]

Microsoft provides the orial content for MSDN Magazine, a monthly publication. The magazine was created as a merger between Microsoft Systems Journal (MSJ) and Microsoft Internet Developer (MIND) magazines in March 2000.|[21]

MSJ back issues are available online.[22]MSDN Magazine was available as a print magazine in the United States, and online in 11 languages. The last issue of the magazine was released in November 2019.[23]

Microsoft Systems Journal[]

Microsoft Systems Journal[24] was[25] a 1986-founded[26] bi-monthly Microsoft magazine.

History[]

MSDN was launched in September 1992[27] as a quarterly, CD-ROM-based compilation of technical articles, sample code, and software development kits. The first two MSDN CD releases (September 1992 and January 1993) were marked as pre-release discs (P1 and P2, respectively).[28] Disc 3, released in April 1993, was the first full release. In addition to CDs, there was a 16-page tabloid newspaper, Microsoft Developer Network News, ed by Andrew Himes, who had previously been the founding or of MacTech, the premiere Macintosh technology journal.[29] A Level II subscription was added in 1993, that included the MAPI, ODBC, TAPI and VFW SDKs.[30]

MSDN logo, 2001–2009

MSDN2 was opened in November 2004 as a source for Visual Studio 2005API information, with noteworthy differences being updated web site code, conforming better to web standards and thus giving a long-awaited improved support for alternative web browsers to Internet Explorer in the API browser. In 2008, the original MSDN cluster was retired and MSDN2 became msdn.microsoft.com.[31]

Dr GUI and the MSDN Writers Team[]

In 1996, Bob Gunderson began writing a column in Microsoft Developer Network News, ed by Andrew Himes, using the pseudonym 'Dr.GUI'. The column provided answers to questions submitted by MSDN subscribers. The caricature of Dr. GUI was based on a photo of Gunderson. When he left the MSDN team, Dennis Crain took over the Dr. GUI role and added medical humor to the column. Upon his departure, Dr. GUI became the composite identity of the original group (most notably Paul Johns) of Developer Technology Engineers that provided in-depth technical articles to the Library. The early members included: Bob Gunderson, Dale Rogerson, Rüdiger R. Asche, Ken Lassesen, Nigel Thompson (a.k.a. Herman Rodent), Nancy Cluts, Paul Johns, Dennis Crain, and Ken Bergmann. Nigel Thompson was the development manager for Windows Multimedia Extensions that originally added multimedia capabilities to Windows. Renan Jeffreis produced the original system (Panda) to publish MSDN on the Internet and in HTML instead of the earlier multimedia viewer engine. Dale Rogerson, Nigel Thompson and Nancy Cluts all published MS Press books while on the MSDN team. As of August 2010, only Dennis Crain and Dale Rogerson remain employed by Microsoft.

See also[]

References[]

Msdn
  1. ^kexugit. 'Welcome to docs.microsoft.com'. docs.microsoft.com. Retrieved 2019-12-29.
  2. ^Martin, John (2008-08-27). 'Microsoft is Planning Much More Than Just Social Bookmarking'. Microsoft TechNet. Archived from the original on 2009-08-01. Retrieved 2009-05-28.
  3. ^'MSDN Worldwide'. Microsoft. Retrieved 2009-05-28.
  4. ^'MSDN Blogs'. Microsoft.
  5. ^'Microsoft Download Center: Windows, Office, Xbox & More'. Microsoft.
  6. ^'Download MSDN Library for Visual Studio 2008 SP1 from Official Microsoft Download Center'. Microsoft.
  7. ^Mark J. Price: C# 7 and .NET Core: Modern Cross-Platform Development Packt Publishing Ltd, 2017, p. 126
  8. ^Jonathan Allen. MSDN/TechNet Being Replaced by Open Source Project docs.microsoft.com InfoQ News
  9. ^'.NET API documentation moved from MSDN to docs.microsoft.com'. Microsoft.
  10. ^'The Visual Studio Blog'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  11. ^'IEBlog'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  12. ^'Windows PowerShell Blog'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  13. ^'Engineering Windows 7'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  14. ^'Building Windows 8'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  15. ^'Michael Howard's Web Log'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  16. ^'The Old New Thing'. blogs.msdn.com. Archived from the original on 29 May 2020. Retrieved 19 December 2020.Cite journal requires |journal= (help)
  17. ^'Archived MSDN and TechNet Blogs'. docs.microsoft.com. 29 May 2020. Retrieved 19 December 2020.
  18. ^Martin, John (2008-05-30). 'New Social Bookmarking Feeds in MSDN Dev Centers'. Microsoft TechNet. Archived from the original on 2009-03-14. Retrieved 2009-05-28.
  19. ^ ab'MSDN End User License Agreement'(PDF). Microsoft. Retrieved 2009-05-28.
  20. ^i.e. 'forever'
  21. ^Rachel England (August 8, 2019). 'Microsoft is closing its long-running MSDN developer magazine'.
  22. ^Homepage of Microsoft Systems Journal on MSDN. Content of issues dating from 1996 onwards is still available.
  23. ^Axon, Samuel (2019-08-07). 'MSDN Magazine will publish its last issue, ending a Microsoft developer era'. Ars Technica. Retrieved 2019-08-08.
  24. ^ISSN 08999-9932
  25. ^Eric Lai (January 10, 2006). 'Scammers tout now-defunct Microsoft magazine to developers'. Computerworld.
  26. ^'Microsoft's MSDN Magazine is shutting down after more than 30 years'. Microsoft Systems Journal started way back in 1986
  27. ^Info World August 1992, bottom-left of page 8
  28. ^Photo of MSDN CDs 1-10
  29. ^Stuart J. Johnston (August 3, 1992). 'Microsoft initiates Developer Network service'. InfoWorld. p. 8.
  30. ^Stuart J. Johnston (November 29, 1993). 'Microsoft launches Network Level II'. InfoWorld. p. 5.
  31. ^Larry W Jordan Jr (2008-04-29). 'MSDN: 'The Highlander' and there will be only one!'. MSDN Blogs. Archived from the original on 2009-05-31. Retrieved 2009-05-28.

External links[]

  • Official website (Archive)
-->

Source-initiated subscriptions allow you to define a subscription on an event collector computer without defining the event source computers, and then multiple remote event source computers can be set up (using a group policy setting) to forward events to the event collector computer. This differs from a collector initiated subscription because in the collector initiated subscription model, the event collector must define all the event sources in the event subscription.

When setting up a source-initiated subscription, consider whether the event source computers are in the same domain as the event collector computer. The following sections describe the steps to follow when the event sources are in the same domain or not in the same domain as the event collector computer.

Note

Any computer in a domain, local or remote, can be an event collector. However, when choosing an event collector, it is important to select a machine that is topologically close to where the majority of the events will be generated. Sending events to a machine at a distant network location on a WAN can reduce overall performance and efficiency in event collection.

Setting up a source-initiated subscription where the event sources are in the same domain as the event collector computer

Both the event source computers and the event collector computer must be configured to set up a source initiated subscription.

Note

These instructions assume that you have administrator access to the Windows Server domain controller serving the domain in which the remote computer or computers will be configured to collect events.

Configuring the event source computer

  1. Run the following command from an elevated privilege command prompt on the Windows Server domain controller to configure Windows Remote Management:

    winrm qc -q

  2. Start group policy by running the following command:

    %SYSTEMROOT%System32gpedit.msc

  3. Under the Computer Configuration node, expand the Administrative Templates node, then expand the Windows Components node, then select the Event Forwarding node.

  4. Right-click the SubscriptionManager setting, and select Properties. Enable the SubscriptionManager setting, and click the Show button to add a server address to the setting. Add at least one setting that specifies the event collector computer. The SubscriptionManager Properties window contains an Explain tab that describes the syntax for the setting.

  5. After the SubscriptionManager setting has been added, run the following command to ensure the policy is applied:

    gpupdate /force

Msdn Subscription Azure

Configuring the event collector computer

  1. Run the following command from an elevated privilege command prompt on the Windows Server domain controller to configure Windows Remote Management:

    winrm qc -q

  2. Run the following command to configure the Event Collector service:

    wecutil qc /q

  3. Create a source initiated subscription. This can either be done programmatically, by using the Event Viewer, or by using Wecutil.exe. For more information about how to create the subscription programmatically, see the code example in Creating a Source Initiated Subscription. If you use Wecutil.exe, you must create an event subscription XML file and use the following command:

    wecutil csconfigurationFile.xml

    The following XML is an example of the contents of a subscription configuration file that creates a source-initiated subscription to forward events from the Application event log of a remote computer to the ForwardedEvents log on the event collector computer.

    Note

    When creating a source initiated subscription, if AllowedSourceDomainComputers, AllowedSourceNonDomainComputers/IssuerCAList, AllowedSubjectList, and DeniedSubjectList are all empty, then 'O:NSG:NSD:(A;;GA;;;DC)(A;;GA;;;NS)' will be used as the default security descriptor for AllowedSourceDomainComputers. The default descriptor grants members of the Domain Computers domain group, as well as the local Network Service group (for the local forwarder), the ability to raise events for this subscription.

To validate that the subscription works correctly

  1. On the event collector computer complete the following steps:

    1. Run the following command from an elevated privilege command prompt on the Windows Server domain controller to get the runtime status of the subscription:

      wecutil gr<subscriptionID>

    2. Verify that the event source has connected. You might need to wait until the refresh interval specified in the policy is over after you create the subscription for the event source to be connected.

    3. Run the following command to get the subscription information:

      wecutil gs<subscriptionID>

    4. Get the DeliveryMaxItems value from the subscription information.

  2. On the event source computer, raise the events that match the query from the event subscription. The DeliveryMaxItems number of events must be raised for the events to be forwarded.

  3. On the event collector computer, validate that the events have been forwarded to the ForwardedEvents log or to the log specified in the subscription.

Forwarding the security log

To be able to forward the Security log you need to add the NETWORK SERVICE account to the EventLog Readers group.

Setting up a source initiated subscription where the event sources are not in the same domain as the event collector computer

Note

These instructions assume that you have administrator access to a Windows Server domain controller. In this case, since the remote event collector computer or computer(s) are not in the domain served by the domain controller, it is essential to start an individual client by setting Windows Remote Management to 'automatic' using Services (services.msc). Alternatively, you can run 'winrm quickconfig' on each remote client.

The following prerequisites must be met before the subscription is created.

  1. On the event collector computer, run the following commands from an elevated privilege command prompt to configure Windows Remote Management and the Event Collector service:

    winrm qc -q

    wecutil qc /q

  2. The collector computer should have a server authentication certificate (certificate with a server authentication purpose) in a local computer certificate store.

  3. On the event source computer, run the following command to configure Windows Remote Management:

    winrm qc -q

  4. The source machine should have a client authentication certificate (certificate with a client authentication purpose) in a local computer certificate store .

  5. Port 5986 is opened on the event collector computer. To open this port, run the command:

    netsh firewall add portopening TCP 5986 'Winrm HTTPS Remote Management'

Certificates requirements

  • A server authentication certificate has to be installed on the Event Collector computer in the Personal store of the Local machine. The subject of this certificate has to match the FQDN of the collector.

  • A client authentication certificate has to be installed on the Event Source computers in the Personal store of the Local machine. The subject of this certificate has to match the FQDN of the computer.

  • If the client certificate has been issued by a different Certification Authority than the one of the Event Collector then those Root and Intermediate certificates needs to be installed on the Event Collector as well.

  • If the client certificate was issued by an Intermediate certification authority and the collector is running Windows 2012 or later you will have to configure the following registry key:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSchannelClientAuthTrustMode (DWORD) = 2

  • Verify that both the server and client are able to successfully check revocation status on all certificates. Use of the certutil command can assist in troubleshooting any errors.

Msdn Vs Visual Studio Subscription

Find more information in this article: https://technet.microsoft.com/library/dn786429(v=ws.11).aspx

Setup the listener on the Event collector

Msdn Subscription Benefits

  1. Set the certificate authentication with the following command:

    winrm set winrm/config/service/auth @{Certificate='true'}

  2. A WinRM HTTPS listener with the server authentication certificate thumb print should exist on the event collector computer. This can be verified with the following command:

    winrm e winrm/config/listener

  3. If you do not see the HTTPS listener, or if the HTTPS listener's thumb print is not same as the thumb print of the server authentication certificate on collector computer, then you can delete that listener and create a new one with the correct thumb print. To delete the https listener, use the following command:

    winrm delete winrm/config/Listener?Address=*+Transport=HTTPS

    To create a new listener, use the following command:

    winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname='<FQDN of the collector>';CertificateThumbprint='<Thumb print of the server authentication certificate>'}

Configure certificate mapping on the Event Collector

Msdn Subscription Os

  1. Create new local user and add it to the local Administrators group.

  2. Create the certificate mapping using a certificate that is present in the machine’s “Trusted Root Certification Authorities” or “Intermediate Certification Authorities”.

    This is the certificate of the Root or Intermediate CA that issued the certificates installed on the Event Source computers (to avoid confusion, this is the CA immediately above the certificate in the certificate chain):

    winrm create winrm/config/service/certmapping?Issuer=<Thumbprint of the issuing CA certificate>+Subject=*+URI=* @{UserName='<username>';Password='<password>'} -remote:localhost

  3. From a client test the listener and the certificate mapping with the following command:

    winrm g winrm/config -r:https://<Event Collector FQDN>:5986 -a:certificate -certificate:'<Thumbprint of the client authentication certificate>' Download chromecast app for mac.

    This should return the WinRM configuration of the Event collector. Do not move past this step if the configuration is not displayed.

    What happens at this step?

    • The client connects to the Event Collector and sends the specified certificate
    • The Event Collector looks for the issuing CA and checks if the is a matching certificate mapping
    • The Event Collector validates the client certificate chain and revocations status
    • If the above steps succeeds the authentication is completed.

Note

You might get an Access denied error complaining about the authentication method, which could be misleading. To troubleshoot, check the CAPI log on the Event Collector.

  1. List the configured certmapping entries with the command:winrm enum winrm/config/service/certmapping

Event Source computer Configuration

  1. Logon with an administrator account and open the Local Group Policy Editor (gpedit.msc)

  2. Navigate to the Local Computer PolicyComputer ConfigurationAdministrative TemplatesWindows ComponentsEvent Forwarding.

  3. Open “Configure the server address, refresh interval, and issuer certificate authority of a target Subscription Manager” policy.

  4. Enable the policy and click the SubscriptionManagers “Show..” button.

  5. In the SubscriptionManagers window enter the following string:

    Server=HTTPS://<FQDN of the Event Collector server>:5986/wsman/SubscriptionManager/WEC,Refresh= <Refresh interval in seconds>,IssuerCA=<Thumbprint of the issuing CA certificate>

  6. Run the following command line to refresh Local Group Policy settings:Gpupdate /force Atomic number and mass number list.

  7. These steps should produce event 104 in your source computer Event Viewer Applications and Services LogsMicrosoftWindowsEventlog-ForwardingPluginOperational log with the following message:

    'The forwarder has successfully connected to the subscription manager at address <FQDN>followed by event 100 with the message: 'The subscription <sub_name> is created successfully.'

  8. On the Event Collector, the Subscription Runtime Status will show now 1 Active computer.

  9. Open the ForwardedEvents log on the Event Collector and check if you have the events forwarded from the Source computers.

Grant permission on the private key of the client certificate on the Event Source

  1. Open the Certificates management console for Local machine on the Event Source computer.
  2. Right click on the client certificate then Manage Private keys.
  3. Grant Read permission to the NETWORK SERVICE user.

Event subscription configuration

  1. Open Event Viewer in the Event Collector and navigate to the Subscriptions node.
  2. Right-click Subscriptions and choose “Create Subscription…”
  3. Give a name and an optional description for the new Subscription.
  4. Select “Source computer initiated” option and click “Select Computer Groups…”.
  5. In Computer Groups click on “Add Non-Domain Computers…” and type the event source hostname.
  6. Click “Add Certificates…” and add the certificate of the Certification authority that issue the client certificates. You can click in View Certificate to validate the certificate.
  7. In Certificate Authorities click OK to add the certificate.
  8. When finished adding Computers click OK.
  9. Back to the Subscription Properties, click in Select Events..
  10. Configure the Events Query Filter by specifying the event level(s), event log(s) or event source(s), the event ID(s) and any other filtering options.
  11. Back to the Subscription Properties, click on Advanced..
  12. Choose one of the optimization options for event delivery from the Source Event to the Event Collector, or leave the default Normal:
    1. Minimize Bandwidth: Events will be delivered will less frequency to save bandwidth.
    2. Minimize Latency: Events will be delivered as soon as they occur to reduce events latency.
  13. Change the Protocol to HTTPS and click OK.
  14. Click OK to create the new subscription.
  15. Check the runtime status of the Subscription by right-clicking and choosing “Runtime Status”