Am 10. und 11. Mai 2016 findet der 19. Effiziente Staat im dbb forum in Berlin statt.

Der Effiziente Staat als Kongressmesse für die digitale Verwaltung greift 2016 das Thema Smart Government, der intelligenten Vernetzung von Regierungs- und Verwaltungshandeln, auf um auch in Deutschland den Diskurs hierzu anzustoßen. Spannende und vielfältige Vorträge warten auf Sie:

• Erleben Sie am 10. Mai 2016 die Keynote von Thomas Langkabel, National Technology Officer, Microsoft Deutschland GmbH, zum Thema "Smart Efficiency, Smart Innovation, Smart Security "

• Lassen Sie sich am Dienstagnachmittag beim Forum „Private vs. Public: Cloud-Strategien für die öffentliche Verwaltung“  von Thomas Langkabel, National Technology Officer, Microsoft Deutschland GmbH, mit ihrem Beitrag „Microsoft Clouds – Sie haben die Wahl“ überzeugen und

• verpassen Sie am Mittwoch nicht das Forum „Smart und vernetzt – eine digitale Agenda für Kommunen“ und den interessanten Beitrag „Digitale Transformation von Kommunen – neue Geschäftsmodelle“ von Prof. Dr.  Dr. e.h. Lutz Heuser, CEO & CTO von unserem Partner [ui!]urban institute

Today’s Tip…

When you get the following error message…

HTTP 400 - Bad Request (Request Header too long)

This is most common when the user is a member of many Active Directory user groups. When a user is a member of a large number of active directory groups the Kerberos authentication token for the user increases in size. The HTTP request that the user sends to the HTTP server contains the Kerberos token in the WWW-Authenticate header, and the header size increases as the number of groups goes up.  If the HTTP header or packet size increases past the limits configured in IIS, IIS may reject the request and send this error as the response.

You can resolve this by performing the steps in the following KB article…

https://support.microsoft.com/en-us/kb/2020943

When I go out to customers, I always like to see how the top collections are populated (All Servers or All Workstations).

This is something most customers do immediately after setting up Configuration Manager, build an all desktops collection and all servers to divide clients and set permissions. Even though this is such a common action within ConfigMgr, I feel most admins don’t put enough foresight into these collections.

You are probably asking, Cameron, “Why does it matter?”

Well the answer is simple: Performance and Security

Performance

Performance matters when you have several thousand collections. Writing the most efficient query, especially at the top for your collection tree, is important. You can waste collection evaluation cycles with poorly written queries, which can end up being detrimental in a large scale environment. What makes an efficient query? Well, obviously the variables of the situation depend, but just know:

• Integer comparison is faster than a string comparison

• Equals are faster than like

Now this doesn’t fit every scenario but I highly recommend using the Collection Evaluation tool in the Configuration Manager 2012+ toolkit. This will tell you the length of time it takes to run your query in a collection, and the state of all other collection.

Security

Security matters, especially when you need to lock down who can access different collections and manage those collections. RBAC has been a great addition but still the most common action here is separate workstations from servers. What about Domain Controllers? For customers who use ConfigMgr to manage and patch their Domain Controllers, who has access to deploy to your DCs? Can they deploy packages, applications or compliance settings? Something to keep in mind when managing the most important servers in your entire infrastructure.

Ok enough talk, let’s get this going!

Microsoft Windows NT % Server\Workstation %

The most common method I have seen to date going all the way back to SMS 2003 is to use the System Resource – Operating System Name and Version, like below.

While this works, the question I pose, is this the best solution? This would give you all the workstation operating systems records, and we can do something very similar to give us all the server clients as well. How do you separate out your domain controllers? I don’t want to write a sub-select query or query other properties having to use the % and is like operator. The simplest, most efficient way I have found is using an attribute called ProductType.

Win32_OperatingSystem – ProductType

If you use your favorite search engine to query Win32_OperatingSystem, a MSDN page should come up in the results. On that page it explains the values of ProductType.

ProductType has 3 simple values based on the type of OS SKU.

1 = Workstations

2 = Domain Controller

3 = Member Server

In Practice

I build 4 collections ALL of them limited to All Desktop and Server Clients. (Here is where I deleted the paragraph dedicated to telling you why you should never use All Systems, but I decided to spare you.) :) Below is screenshots on how to create the different queries needed.

All Desktop Clients (All Workstation Client)

All Non-DC Server Clients

All Domain Controller Clients

The fourth collection is optional but I believe it can be handy when you need a limiting collection for a global server deployment.

All Server Clients

Notice I am using the Include Collection instead of running another query. Two points here:

1) Why write a query that has to be processed twice when you don’t have too?

2) I have found in my lab, the include collection was 1.2 seconds faster in evaluation time then writing a query with multiple values.

Your millage may vary but I am sure you will see similar results.

The Caveat

I know it seemed too good to be true right? The biggest thing to remember here is Win32_OperatingSystem is collected via Hardware Inventory. Which means until we have a client on a machine, we do not have this data to populate the collections. Now in my humble opinion, this is OK. There is no point in creating deployments to machines without clients, since they can’t run the deployment. This can also uncover any client health issues if collection counts are lower than expected.

Hope you enjoyed and thanks everyone for reading!

Cameron

Today’s Tip…

How to add E5 licenses to an existing E3 trial tenant

1. Log into your E3 trial tenant as a company administrator (global admin).
2. Go to E5 trial sign up: https://go.microsoft.com/fwlink/p/?LinkID=698279.
3. If you are not signed in to your E3 trial, click Sign in from the trial sign up page, and enter your E3 trial tenant credentials.
4. Follow the on-screen instructions to add E5 licenses to active users in your trial tenant.
5. E5 licenses will appear as an option when you add new users or edit active users in OAC.

Note: Once you have an E5 subscription, you can follow the steps in the following article to extend your trial.

66.     Jak vložit obrázek z počítače či internetu?

67.     Jak je to s licencí obrázků?

68.     Jak si přiblížit obrázek?

69.     Jak změnit styl vloženého obrázku?

70.     Jak otočit obrázek?     

Today’s Tip…

Huge updates come to the latest installment of Azure AD Connect. Get Azure AD Connect 1.1 now to take advantage of the improvements.

Here are the highlights…

• Reduction in the sync interval to keep your Azure AD in sync with AD on-premises more quickly. Moved from every 3 hours to 30 minutes.
• Support for automatic upgrades with Express Settings only. That’s rights, no more having to install the latest as it will automatically upgrade.
• Modern Authentication protocol now supported. This means MFA is now supported as well as temporary admins leveraging Azure PIM.
• Support for Domain and OU filtering within the wizard.
• Changing users sign in methods. It is now possible to change the method through the Azure AD Connect wizard. Just run the installation wizard again to change the sign-in option.

For more information about this release, check out the official announcement here…

https://blogs.technet.microsoft.com/ad/2016/02/18/azure-ad-connect-1-1-is-now-ga-faster-sync-times-automatic-upgrades-and-more/

Today’s Tip…

The Azure AD Synchronization Tool or also called DirSync will soon be deprecated and will be replaced by Azure AD Connect. To learn more about how you can upgrade from DirSync to Azure AD Connect, check out the following article…

https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnect-dirsync-upgrade-get-started/

Today’s Tip…

Just when you thought DNS could not get any better there are several new features and improvement included in Windows Server 2016 TP4 to get excited about. One notable improvement that will be very useful to troubleshooters and support engineers is the addition of new diagnostic and logging capabilities consisting of both Analytical Events and ETW trace providers.

The good news is that these features have also been backported to Windows Server 2012 R2 DNS!  If you have a 2012 R2 DNS server you can download and install the following package to enable this capability.

Update adds query logging and change auditing to Windows DNS servers

Note Concerning DNS Debug Logging

Prior to the introduction of DNS analytic logs, DNS debug logging was an available method to monitor DNS transactions. That DNS debug logging is not the same as the enhanced DNS logging and diagnostics feature discussed here. 

Analytical Event Logging

Enhanced DNS logging and diagnostics in Windows Server 2012 R2 and later includes DNS Audit events and DNS Analytic events. DNS audit logs are enabled by default, and do not significantly affect DNS server performance. DNS analytical logs are not enabled by default, and typically will only affect DNS server performance at very high DNS query rates. For example, a DNS server running on modern hardware that is receiving 100,000 queries per second (QPS) can experience a performance degradation of 5% when analytic logs are enabled. There is no apparent performance impact for query rates of 50,000 QPS and lower. However, it is always advisable to monitor DNS server performance whenever additional logging is enabled.

Click on the link for a detailed list of DNS Analytic events as well as the steps necessary to enable DNS diagnostic logging once the package is installed.

ETW Logging

DNS logs are compatible with Event Tracing for Windows (ETW) consumer applications such as logman, tracelog, and message analyzer.  You can use ETW consumers such as tracelog.exe with DNS server audit and analytic events by specifying a GUID of {EB79061A-A566-4698-9119-3ED2807060E7}.

Note - You can get tracelog.exe by downloading and installing the Windows Driver Kit (WDK). Tracelog.exe is included when you install the WDK, Visual Studio, and the Windows SDK for desktop apps. For information about downloading the kits, see Windows Hardware Downloads. For example, when you download and install Windows Driver Kit (WDK) 8 and accept the default installation path, tracelog.exe is available at C:\Program Files (x86)\Windows Kits\8.0\Tools\x64\tracelog.exe.  For more information about using tracelog.exe, see Tracelog Command Syntax.

The following command will enable both analytical and audit logging:

tracelog.exe -start Dns -guid #{EB79061A-A566-4698-9119-3ED2807060E7} -level 5 -matchanykw 0xFFFFFFFF -f C:\analytic_audit.etl

While the trace is active, all analytical and audit events will be recorded in the C:\analytic_audit.etl file that was specified on the command line. You can stop tracing by issuing a stop command:

tracelog –stop Dns

After stopping the trace, you can view the .etl file in Event Viewer by clicking Action and then clicking Open Saved Log. AS shown in the following example.

The following example enables just the analytical channel and matches only the keywords to 0x7FFFF:

tracelog.exe -start Dns -guid #{EB79061A-A566-4698-9119-3ED2807060E7} -level 5 -matchanykw 0x7FFFF -f C:\analytic.etl

Using this syntax, a logging level of 5 is used. The following logging levels are available:

Call to Action

At your first opportunity familiarize yourself with the process of gathering and analyzing DNS ETW logging.  It is very economical in terms of resource consumption compared to traditional DNS debug logging and can be very useful in troubleshooting and forensic efforts. 

Your feedback is very important is well.  If you encounter a scenario where information not currently captured by the trace would be helpful, let us me know!  The DNS PG is very active in the area of diagnostics and if your idea would help reduce the time it takes to resolve an issue they would be very interested in hearing it! 

Review the following article for more information on DNS Analytical Logging and other diagnostics.

https://technet.microsoft.com/en-us/library/dn800669.aspx

Today’s Tip…

Yesterday’s tip discussed some of the new analytics available for Windows Server 2016 and back ported to Windows Server 2012 R2.  I couldn’t resist following up with an article on one of the scenarios mentioned in that tip, Network Forensics.

Below is a link to a very informative article written by key members of the DNS Product Group explaining a practical application of analytics to solve a real-world problem.  There is some really good stuff here including

• How DNS intel can be used to compromise a network, and how analytics data can be used by network defenders to detect and investigate such an attack
• Example DNS analytic event logs
• Hardcore performance tips –
  • To what degree analytics can potentially introduce performance degradation, and
  • when to use what method of collection; topics such as tracelog and Windows Event Collection are discussed
• Example of filtering to eliminate less valuable information

Check out the following article for all this and more: Network Forensics with Windows DNS Analytical Logging

And for resources referenced in this and yesterday’s tip.

• DNS Logging and Diagnostics
• Update adds query logging and change auditing to Windows DNS servers
• Windows Event Collector

Final Thoughts

The article Network Forensics with Windows DNS Analytical Logging represents an excellent example of taking a real world scenario, tools, and data and turning it into a teaching and learning opportunity.  I think we can all agree that information is easier to retain, particularly on a topic as nuanced as trace and log analysis, when presented in the context of solving real-world problems.

Do you have scenarios and examples where you used logging and analytics to do something amazing?  Get to the bottom of a deep mystery?  Eek just a bit more performance out of that app or server? 

Doesn’t have to be DNS or even network related.  Let us know!  There is a good chance that your experiences could be turned into a teaching tools for others while driving a better product and customer experience in the long run.

Today’s Tip…

In keeping with this weeks ‘Diagnostics’ theme, I wanted to dust off a really good article written some time ago by Gopal Krishnan on Setting up Port Mirroring to Capture Mirrored Traffic on a Hyper-V Virtual Machines.

In a typical (non-promiscuous) capture, you are only seeing communications from the perspective of the host on which capture software is running and no further.  Furthermore, this capture is representative of the hosts network stack only, and does not account for anything the NIC hardware may be doing, let alone any network media or devices along the transit path.  When enabled, port mirroring ‘extends’ your, adding perspective by peering onto the stack of the switch itself to see what it sees.  Many times this may shed light on issues not readily identifiable by a simple host capture.  Issues such as faulty or misconfigured hardware are more easily identified. 

Port–mirroring works by, well, ‘mirroring’ a port on the switch, replicating all the traffic it sees to another port or VLAN where the host running the capture software can see it.  In the following illustration, Node A’s switch-port is mirrored.  All traffic that traverses this port is copied to Node D’s switch-port, allowing capture from the connected host using Microsoft Message Analyzer.

Note: Though there is a modicum of consistency, the steps to configure a port-mirror can vary from vendor to vendor.  Consult your hardware documentation for steps to set up a port mirror.  Also note that port mirroring requires that the switch be a ‘managed’ device, meaning its firmware supports this capabilities among others.   

In his article, Gopal outlines the steps needed to take the scenario one step further and direct the traffic for capture on a Hyper-V virtual machines running on Node D.  Very useful if you have a scenario where it is undesirable to run the capture software on the Hyper-V Host itself.

Setting up Port Mirroring to Capture Mirrored Traffic on a Hyper-V Virtual Machine

Call to Action

Give these steps a try.  Build familiarity with these steps even if you don’t have an immediate scenario where this type of troubleshooting would be beneficial.  Use your newfound knowledge to amaze your friends and colleagues!

71.     Jak nastavit obtékání textu okolo obrázku?

72.     Jak změnit velikost obrázku?

73.     Jak oříznout obrázek?

74.     Jak získat přístup k obrázkům?

75.     Jak vložit snímek obrazovky?

Today’s Tip…

Announcing Microsoft Message Analyzer 1.4

Today we are pleased to announce the Message Analyzer 1.4 release, which specifically focuses on customer feedback, telemetry, and survey data. 

If you are upgrading from a previous version, Message Analyzer will remember your layouts, recent files, filter history, and so on.  However, this means you won’t see the new Profile Layouts mentioned below.  If you are not concerned about your default settings, you can rename app.ApplicationConfiguration.cfg in the %LocalAppData%\Microsoft\MessageAnalyzer directory and restart Message Analyzer to obtain the latest configuration of Layouts, including those used by the Profiles feature.

Below is a list of the specific features and improvements in Message Analyzer v1.4.  Also visit our Video Playlist on Youtube to help get you up to speed.

Customization

Profiles– Often we have heard feedback such as: “When I open an IIS log, can’t you show me IIS related columns of data?”.   The same question can be asked of many other file types that Message Analyzer supports, for example, .etw, .cap, .blg, .evtx, netlogon logs, and so on.  Profiles solve this problem by defining Layout defaults based on the type of data you load.   By using Tools->Options->Profiles, you can further customize the defaults of your working analysis environment for various input file types by creating your own Profiles.  If you prefer to not use the Profiles feature, you can always unselect the Use Advanced Profiles check box shown in the Figure that follows.

Furthermore, all built-in Profiles are configured with a Default Layout for the Grouping viewer. This means that the Grouping viewer will automatically display the Default Layout whenever you load data from the input file type for which the Profile is configured, providing that the Profile is also configured to automatically open the Grouping viewer. In the case of the Chart viewer, the built-in Profiles are also configured with a Default chart Layout; however, you will need to manually select the Default layout item (see the Charts figure ahead) for the Chart viewer in the New Viewer drop-down list to display the Layout that is configured in the Profile, that is, after you load data from the specific input file type for which the Profile is configured.  Note that you can configure your own default Layouts for these viewers in any new Profile that you create.

Window Layouts– Somewhat related to Profiles, Window Layouts quickly arrange Tool Window presets in various configurations to customize your working environment.  With this feature, you can understand specialized tools by exploring each built-in Window Layout.  The Simple Layout is a great place to start if you are a beginner. The Network Layout is perhaps the next step and is useful for viewing network stack information.  The Advanced Layout exposes many features, such as the Compare Fields, Selection, and Bookmarks Tool Windows.  Select one, customize it, and Message Analyzer will save your custom Layout when you exit the application.

Charts– Previously, Charts were a combination of visualizer components put together in one view.  Now we’ve separated these components for consistency with our paradigm where each data viewer has its own set of Layouts.  For charts, each Layout represents a single visualizer component that provides a top-level data summary or statistics based on a message type, fields, properties, and a pre-configured formula to cover a particular analysis scenario.  If you miss the old charts, you can still display them from the Charts (Deprecated) drop-down list.

Improvements

Filtering Toolbar– We heard your feedback that you want a filter bar at the top.  We also realized that you got confused when there were multiple views of data, each with separate filters.  To solve this, we have included a separate Filtering toolbar at the top of each viewer tab.  For most views, the toolbar is opened by default with one blank filter.  But you can use the Add Filter button on the Filtering toolbar to add one or more of various filter types that include a view Filter, Time Filter, and Viewpoint Filter, as shown in the Figure that follows.

Process Name Improvements– In the previous Message Analyzer version 1.3.1, we added the ability to read process name information, that is, if the special Windows-Kernel-Trace provider was available.  Now you can capture process names natively with Message Analyzer.  Additionally, we support process name information in .cap files that were captured using Network Monitor and we also display the ICONs in the Grouping view, as shown in the Figure below.

Features

Flat Message List– Message Analyzer reduces noise in a trace by automatically condensing the traffic so that fragmentation packets are hidden and requests and responses are grouped together in top-level Operation nodes.  By clicking the Flat Message List button, you can change the mode to show you the raw traffic that is reorganized in the chronological order in which the messages were originally captured.  Messages are still reassembled, but Operations are removed and the fragments are shown in their original sequence.  This mode enables you to view traffic the way Network Monitor and other protocol analyzers display it, and can help you compare data to other tools in a way that is familiar to you.

P-Mode– Promiscuous mode is supported by many network Ethernet vendors.  P-Mode enables Message Analyzer to see traffic that is not directly targeted to your machine.  If you can configure your switch to forward packets from another machine, or perhaps all network traffic if you are brave and can handle that much traffic, you can enable this option in the Advanced Settings - Microsoft-Windows-NDIS-PacketCapture provider configuration dialog, which is accessible from the New Session dialog, as shown in the Figure below.

Auto IP Address Resolution– This feature uses captured name resolution network traffic and translates it into friendly names.  For instance, when a DNS request resolves 192.168.1.1 to MSN.COM, Message Analyzer will now use that friendly name in the UI instead of the IP address.

Time Offset– Message Analyzer now provides a new Global Property called DeltaFromFirst, which enables you to measure the time offset from the beginning of a trace.  You can add the DeltaFromFirst property as a new column in the Analysis Grid for viewing the time data, by using the Field Chooser, as shown in the Figure that follows.

Decoded URLs– URLs can be encoded with escape characters that make them difficult to read.  The Field Data Tool Window has been extended to show a decoded view, which is easier to read.

Enhanced Bit-field Display– Bit-fields are now displayed in the Details Tool Window such that that it is easier to understand where the bits are, and you can also view a description for each bit setting.

Save as Binary– From the Message Data Tool Window, you now have the option to export any hex selection as Binary.  For example, you can export data to save a PNG file, or extract some piece of information that you need to evaluate in other tools.

WPP Symbol Configuration– WPP tracing is a method of instrumenting code to write events and provides information such as source code file name and line number.  But this requires private symbols in order to parse events properly.  Now by using Tools->Options, you can configure the location of TMFs or point directly to your PDB path through a dedicated UI.  The latter option requires a local version of TracePDB, which you also need to reference if you choose that option.

Trace Custom GUIDs– If a provider component doesn’t register with your system, you won’t find it in the System Provider list.  Now Message Analyzer enables you to manually add a GUID for an ETW provider by using the Add Providers feature, as shown in the Figure that follows. Thereafter, the provider will be registered and Message Analyzer will remember it so that you can locate and select the provider quickly during session configuration.

Drag and Drop– You can now drag and drop multiple files from File Explorer and aggregate their data into a single session.  You can still use New Session->Files to filter your data down, or simply use the Edit Session button after you drag and drop, to change what data you import and analyze.

Enhanced OPN Viewer– In the Details Tool Window, you can right-click a field and select Go to <fieldname> Definition to display the field definition in OPN code.  In this context, the OPN viewer has been updated to provide a better viewing experience.  In addition, you can right-click a code entity such as a data type to display a context menu that enables you to search Microsoft documentation for more programmatic information about the particular entity that you selected in the OPN viewer, as shown in the Figure that follows.

Updated Status– The status bar now provides a wait cursor that activates when Message Analyzer is busy processing or capturing data.  Now, even if you don’t have the Session Explorer open, you are still notified when messages are being loaded, captured, or processed, as shown in the Figure that follows.

Your Feedback is Appreciated!

We really appreciate all the feedback you have sent us so far.  Obviously we couldn’t address every request, but be assured that we continue to listen.  You can send feedback using the smiley face icon to the right of the Message Analyzer global menu, or for more complex requests and a dialog, visit our forums on TechNet.  There, you can leave feedback that others can vote on, which helps us prioritize the most popular requests.   In addition, we’ve published a new video series on our YouTube playlist, which we will continue to expand.  Finally, the comprehensive Message Analyzer Operating Guide on TechNet has lots of wonderful information and scenario-based help to get you started.  All of these links are available from the Message Analyzer Start Page or the Help menu.  Be sure to take it for a test drive, and let us hear even more feedback.  Enjoy!

Besucht uns vom 31. Mai bis 2. Juni 2016 im City Cube in Berlin in Halle B am Stand B17.

Microsoft wird neben weiteren Partnern, wie [ui!] Urban Institute und NXP Semiconductors vertreten sein und auf die Themen „Innovative Arbeitswelten“, „Microsoft Cloud Deutschland“, „Microsoft CityNext“ sowie „Internet der Dinge“ eingehen.

Im Rahmen der weltweiten Initiative Microsoft CityNext unterstützt Microsoft gemeinsam mit seinen Partnern Städte, Kommunen und die gesamte öffentliche Hand bei der digitalen Transformation. Es werden Lösungen aufgezeigt, die Betrieb und Infrastruktur transformieren, Bürger und Organisationen einbeziehen sowie die wirtschaftliche Entwicklung und die ökologische Nachhaltigkeit fördern und beschleunigen. Vernetzung ist der Schlüssel zu besseren Bürgerdienstleistungen, effektiveren Prozessen und mehr Kosteneffizienz. IT bietet Städten und Kommunen die Chance, sich grundlegend zu modernisieren und sich in innovative Dienstleistungszentren mit zeitgemäßen Kommunikationsstrukturen zu wandeln.

Wer treibt die digitale Transformation – Menschen oder Technologien? Gerne zeigen wir Gedanken und Ansätze zum innovativen Arbeiten auf und diskutieren diese mit Euch.

Unter dem Motto Smart Cities – Needs & Barriers bietet die Metropolitan Solutionseinen fantastischen Überblick über die Anforderungen und Hindernisse auf dem Weg zu einer intelligenteren Stadt. Stadtverantwortliche und Industrievertreter diskutieren Themen wie offene urbane Plattformen sowie integrierte Stadtplanung und Stadtverwaltung.

Schauen Sie selbst welche Lösungen bereits von Microsoft und seinem CityNext Partner [ui!] Urban Institute in Bad Hersfeld und Darmstadt zum Einsatz kommen: Video.

Verpassen Sie nicht den englischen Beitrag “Secure IoT Management in Urban Spaces“  von Thomas Langkabel, National Technology Officer am 01. Juni 2016 um 14:30 Uhr.

76.     Jak uložit obrázek z dokumentu?

 

77.     Jak najít obrázek či jiný objekt?

78.     Jak do Wordu vložit video?

79.     Jak vytvořit aktivní odkaz na webovou stránku?

80.     Jak vložit záhlaví a zápatí?

Microsoft a mis à jour les différents posters pour ses services infonuagiques.  Vous les trouverez sur ce lien.

81.     Jak mít v dokumentu různá záhlaví?

82.     Jak vložit do dokumentu číslování stránek?

83.     Jak nemít na první stránce číslo stránky?

84.     Jak vložit křížový odkaz?    

 

85.     Jak vložit iniciálu?

This post is intended for advanced Power Query users and M fans.

In case you are not following my blog here, I have published 3 cool tutorials about Power Query functions List.Generate and List.Accumulate, including a useful query that performs Matrix Multiplication, and does it in much better way than the array function MMULT.

In addition, if you ever wondered how to implement a nested loop in Power Query, read here how to do it using List.Generate.

Follow my blog http://datachant.com, for ore good stuff in the future.

See you there,

Gil Raviv

DatsChant..com