Das Elster Whitepaper für Microsoft Dynamics NAV 2016 (Stand: 01.08.2016) ist nun auf Partner Source zum Download bereit:
Das Download-Paket beinhaltet die aktuellsten Stylesheets, das öffentliche Zertifikat der Finanzbehörde, eine Liste der Fehlercodes von der Finanzbehörde und natürlich das Whitepaper selbst.
Mit freundlichen Grüßen
Franziska Fiegler
Microsoft Dynamics Germany
Microsoft Customer Service und Support (CSS) EMEA
I had to leave Germany for a few days because of major meteorlogical issues. Let me share my Nuggets from hot and sunny Spain:
We are working hard to resolve this issue and apologize for any inconvenience.
-Matt
Every week we get customer’s calling us asking who dropped their Azure Sql Database. However, this doesn’t require a call to customer service. You can tell from the activity logs in the portal who dropped a database or a server. In the Windows Azure Portal click on Active Logs:
Then choose your subscription from the Filter bar and set the time window to cover when you think that the database was dropped.
Look for the Delete SQL Database log entry line, then click on the Json tab once that line is selected. In the Json, you can find the database name, in this example it is called “TheMicrophone”, and the caller that deleted it:
What do you know I am to blame for deleting my own database. Drops Microphone. Wayne Out.
{6230289B-5BEE-409e-932A-2F01FA407A92}
In Section 2.2.2.1, Client Device List Announce Request (DR_PRN_DEVICE_ANNOUNCE),
updated the PreferredDosName field description to indicate mandatory
usage of the “PRN” prefix: https://msdn.microsoft.com/en-us/library/mt608579.aspx
In Section 2.2.1.3, Device Announce Header (DEVICE_ANNOUNCE), clarified that the maximum device name length should be 7 characters to account for the null terminator in the PreferredDosName field description: https://msdn.microsoft.com/en-us/library/mt242382.aspx
Final Update: Monday, 15 August 2016 19:45 UTC
A small subset of customer would have experienced intermittent timeouts while accessing Visual Studio Team Services accounts hosted in South Central US region. We identified one of front end service is failing to connect to the database with timeout. We took necessary steps to restore problematic instance and mitigated the issue.
We understand that customers rely on VS Team Services as a critical service and apologize for any impact this incident caused.
Sincerely,
Sudheer K
The SQL Server Data Tools team is pleased to announce an update for SQL Server Data Tools (SSDT) is now available. The SSDT 16.3 release introduces new Tabular Model Explorer, enhancements for Always Encrypted experience with new key management dialogs and various bug fixes.
Get it here:
Download SSDT GA 16.3 for Visual Studio 2015 and Visual Studio 2013
This release will be available through Visual Studio Extensions and Updates notification soon.
Download Data-Tier Application Framework (August 2016)
Release Versioning & Numbering
Releases are now tagged numerically rather than by month. This aligns with the new SSMS policy and simplifies cases where we have multiple releases or hotfixes in a month. This release is 16.3 which means the third update after RTM release. Any hotfix will be 16.3.1 and so on, with our next update (planned for next month) being 16.4.
Analysis Services – Tabular Model Explorer
Tabular Model Explorer lets you conveniently navigate through the various metadata objects in a model, such as data sources, tables, measures, and relationships. It is implemented as a separate tools window that you can display by opening the View menu in Visual Studio, pointing to Other Windows, and then clicking Tabular Model Explorer. The Tabular Model Explorer appears by default in the Solution Explorer area on a separate tab. Tabular Model Explorer organizes the metadata objects in a tree structure that closely resembles the schema of a tabular 1200 model and many more new features. Try the new Tabular Model Explorer in SSDT August update today!
Database Tools – Always Encrypted easy provisioning for Column Master Key and Column Encryption Key
Always Encrypted is a highly anticipated security feature in Azure SQL Database and SQL Server 2016. Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to the Database Engine (SQL Database or SQL Server), significantly enhancing security.
What’s in this release
This release provides new Always Encrypted Key management dialogs to easily add Column Master Key or Column Encryption Key to your database project or a live database in SQL Server Object Explorer. This release supports certificates in Windows Certificate Store. In the upcoming releases, Azure Key Vault and CNG Providers will be supported.
Limitations:
While creating Column Master Key or Column Encryption Key, you may experience that the changes are not reflected on SQL Server Object Explorer immediately after clicking Update Database. To workaround, refresh the database node in SQL Server Object Explorer.
If you try to encrypt a column in a table with data from SQL Server Object Explorer, you may experience a failure. This feature is currently supported only in SSDT database project and SSMS. The support for SQL Server Object Explorer will be enabled in a later release.
Database Tools
| SSDT: Connect bug 1898001 Fixed a column description issue with 128 character limitation |
| SSDT: Fixed an issue where publishing a database from VS did not apply DatabaseServiceObjective property in the publish profile xml |
| SSDT: Connect bug 2900167 Fixed a unit test issue for incorrectly leaving temp files |
| SSDT: Fixed an issue where Retention Period combo box on Database Settings is truncated |
| SSDT: Fixed an issue for the missing verification of empty old password on SQL CLR project properties while changing the password |
| DACFx: Fixed an issue about DACFx compatibility level is not updated for SqlAzureV12 error |
| DACFx: Fixed an issue where IsAutoGeneratedHistoryTable property is incorrectly excluded from model comparison |
Analysis Services & Reporting Services
| SSDT: Fixed an issue that Tabular model cannot be saved when the server connection is lost |
| SSDT: Fixed an issue that SSDT becomes unresponsive due to a possible infinite loop issue in AS |
| SSDT: Fixed a DAX expression issue that caused inconsistent behaviors based on how you commit the expression |
| SSDT: Fixed a VS crash issue when creating KPIs |
| SSDT: Fixed an issue that generated invalid reports for SQL Server 2008 R2, 2012 and 2014 |
| SSDT: Fixed a Hierarchy order issue that caused an infinite loop error for .dwpro project |
| SSDT: Fixed a RS RDL issue where downgrading RDL required a full rebuild which caused user’s confusion |
| SSDT: Fixed a KPI issue where Hide From Client Tools had no effect |
To prevent an accidental data loss, deployment that requires data motion on a table with Row Level Security is blocked by default. To override the default behavior, use SqlPackage.exe with option /p:AllowUnsafeRowLevelSecurityDataMovement=true.
If you have any question or feedback, please ping @sqldatatools on twitter, visit our forum and for bugs please create bug reports on our Microsoft Connect page. We are fully committed to improve the SSDT experience and look forward to hearing from you!
We are working hard to resolve this issue and apologize for any inconvenience.
-Arvind
I’ve mentioned before to be careful about NLS Locale & Culture Data Churn, in that Locale Data Should Not Be Considered Stable, but there’s an interesting aspect of that in Windows 10.
Windows 10 Supports all Locales – Kinda.
We kept getting asked for more and more locale/language data and applications kept running into trouble when NLS didn’t think the tag existed. So we made Windows 10 return the best data it knows about for any valid NLS locale tag that it runs into.
“In the old days,” there used to be a somewhat finite set of locales that operating systems supported or had collected data on. They might differ a little, but the sets were somewhat limited. In more modern systems however, we start encountering valid data that is tagged in all sorts of interesting and completely valid data that we don’t have in-box support for.
That’s a problem because then your document says “Hey, I was written in Hawaiian” and the app goes “what’s that?” and blows up or refuses to load the document.
“Constructed” Locales
So, in Windows 10, if you pass in a well-formed tag, then we’ll give you the best answer that we can. So if your document says “I’m tagged with the Fijiian dialect of Klingon” we go “Hmm, well, okay then” and let you fumble on – but we don’t blow up.
We do that with “contructed” locales. When we get a locale we don’t recognize, we try our best to find reasonable data for it. Since we’ve started using the CLDR data, we have a lot more native data, but still you might ask for something we don’t have. If we have the root language, like you asked for “en-FJ” (English as spoken in Fiji), then we’d look for en-FJ and not find it. So then we’d fall back to “en”, (which looks to us a lot like en-US), and use that as a basis for your en-FJ locale.
That means that some strings might be reasonable, like you’d have “Monday”, “January”, etc. as one might expect for en-FJ. But we might not know the country name or other country based aspects.
Also, it’s possible that we don’t have a clue, like if you passed in “tlh-001” (Klingon (World)) we’d fail to find any data. Then we’d return generic data based on our invariant locale.
Good Enough
Getting by with the constructed data is good enough for lots of scenarios, but it may not provide the best results. For improved results folks can use the Locale Builder tool, or, even better, work with the CLDR to populate locales with appropriate data for your community’s needs.
Those suggestions also imply that eventually the data might improve, whether from the user installing a custom locale or the next Windows 10 update adding improved locale data from CLDR. Which again means that the data you get back might change in the future, hopefully for the better.
因為我們喜歡更改版本名字並不時搬移一些功能，我想試著簡明地概述 Visual Studio 2015 Enterprise 與 Visual Studio 2015 Professional。
作為背景，2015 的版本對 Visual Studio IDE 陣容作出了一些改變，用新的 Enterprise 版本取代了 Premium 與 Ultimate 版本。這表示很多原本使用 Premium 的人現在叫做 Enterprise，而看看那些您會選擇 Enterprise 的原因，這也會有幫助於回答「現在我升級為 Enterprise 了，那裡面到底有什麼？」。
IntelliTest 是一個 2015 的全新功能，它可以幫助您分析原始碼並建立單元測試，來達到 100% 的程式碼覆蓋率，對於該程式碼的每一個路徑。
這表示您可以更輕易地讓更多程式碼被單元測試所覆蓋，幫助您新增單元測試到沒有單元測試的程式碼，並且讓掌握為新的程式碼建立單元測試很容易。這並不代表您將不用再寫一個單元測試，我認為這是幫助您產生核心的單元測試，讓您能基於您的領域知識專注在一些特別的測試與情境。
您可以設定它允許例外，覆蓋物件的創建等等。
它可以與 MS Tests、NUnit、xUnit 和其他任何在 Visual Studio 中提供 adapter 的測試 framework 一起使用。目前僅限於 C#。
這裡有一個35分鐘的影片來更深入了解 IntelliTest。
IntelliTrace 是一個歷程或事後分析的偵錯技術，幫助我們處理「我不能重新產生它」的問題，通常跨越開發與測試環境。它在 2010 被引入所以並不新，而且它可以被使用在開發、測試與生產環境。
一個簡單的使用例子：
測試者在測試環境中發現一個錯誤。測試者啟用 IntelliTrace 再重新產生這個錯誤，而這個錯誤發生時就會包含 IntelliTrace 的記錄檔。這個記錄檔會包含測試環境的呼叫與事件。
開發者在 Visual Studio Enterprise 開啟錯誤與 IntelliTrace 的記錄檔，可以檢視引發的例外與那些例外的堆疊追蹤。開發者可以選擇任何例外來偵錯，Visual Studio 將會進入到偵錯模式，並停止執行在您選擇的例外發生的那行程式碼。開發者可以向前或向後檢查程式碼，來了解發生什麼事。
主要優點 – 開發者不需要為了了解如何修復一個錯誤，而努力產生一樣的條件以複製出相同錯誤。IntelliTrace 讓開發者可以伴隨著偵錯進行，即使這之後才會發生而且在不同的環境。對於基於環境所產生的問題（例如：可以在測試環境被重新產生，但在開發環境不行），這可以節省相當多時間。
這需要 .NET 2.0 或更高的 C# 或 VB.NET 和在 ASP.NET、Microsoft Azure、Windows Forms、WCF、WPF、Windows Workflow、SharePoint 與 64-bit 應用程式下工作。您不需要 Enterprise 來收集 IntelliTrace 的資料，但您需要 Enterprise 來使用它。
這裡有更多相關的內容，MSDN 文件與 12分鐘的概覽影片。
Enterprise 包含了架構工具而這些分成兩個陣營；UML 與 non-UML 工具。
UML 工具提供很多不同種類的圖表，像是 Class、Sequence、Activity、Use Case 與 Component 圖表，而且允許正向與反向工程。
Non-UML 工具為 Code Maps 與 Layer Diagrams。這些不同於 UML 工具，是根本上地涉及底層的原始碼。Code Maps 讓您可以視覺化地了解與探索您的程式碼。
為什麼這很有用？它讓您可以建構對於您程式不同方面關係的理解，而不需要實際去讀那些原始碼。Code Maps 讓您從組件深入到命名空間、類別、方法與深入到底層的原始碼，也可以過濾掉那些您不感興趣的元素，像是測試程式碼或系統組件。
您可以新增您自己的註釋與分組，重新排列圖表與分享給其他人，透過 email、儲存成圖表或直接在 Visual Studio 中。一個 Professional 的使用者可以檢視 Code Maps 但不能編輯它們。
這對於一個剛新加入一個專案的人或是當您要更改您並不熟悉或可能沒辦法記得的程式碼來說相當有幫助。
一個經常被忽略的功能就是您也可以用 Code Maps 來偵錯，而這真的很有幫助，在偵錯時不需要在腦中持續追蹤程式碼。
Code Maps 適用於 .NET 與 C/C++。為了讓您更清楚了解，這裡有一個 9 分鐘的概覽影片與一些相關的文件。
您想要持續部署您的程式碼到多個異質的環境，無論混合多種您需要的自動與人工審核機制，或者履行各種行為在每個環境之中(預備、佈署、測試等環境)?
這也就是在 Visual Studio 2015 新的版本管理工具所提供的。版本管理組成 Visual Studio DevOps 支援的一個核心部分，提供持續部署的支援與補充新的建置系統、共享同樣的跨平台代理程式。
要建立與編輯發行定義、定義環境、需要的佈署步驟、批准等等是需要 Enterprise 版本。這裡有個 2 分鐘的概覽影片或這個 30 分鐘更深入的影片。
來簡單地總結，您可以在 Enterprise 取得所有測試工具。換一種說法：
前三個項目包含在 Microsoft Test Professional，是 Enterprise 版本的一部分。我將不會在這提到，但您可以在這裡了解更多相關資訊。對於 Enterprise 來說獨特的是自動化功能測試和負載與效能測試。
Visual Studio 自動化功能測試的工具為 Coded UI。正如它名字暗示的，這會建立自動化測試（即包含自動驗證），並將他們記錄為程式碼 – C# 或 VB.NET。當您執行操作或在程式碼等級用重複使用測試建立測試，您可以記錄它們。您也可以用手動測試來建立自動化測試，然後新增憑證。
Coded UI 讓您可以建置驅動應用程式 UI 測試的回歸套件，而要遠端執行這些回歸測試，如在測試環境，甚至是上面討論的發行管理功能的一部分。請注意，遠端執行 Coded UI 測試並不需要 Enterprise 版本，所以其他使用者可以執行它們。這裡有一些文章讓您更了解 Coded UI。
負載與效能測試已經在 Visual Studio 中很長一段時間了，而且發展了很多年。核心的功能是相同的；建立一個情境來測試效能，用某個數量的虛擬使用者在給定的時間內執行一些測試。您可以把網路狀態納入考量（例如：10% 的使用者是在一個很差的網路連線狀態，而他們的體驗如何？）與收集系統效能計數器資訊（CPU、記憶體、硬碟 I/O 等等）：
這裡有一個建立與執行負載測試的教學。
最近的改動包含了選擇使用 Azure 來產生負載的功能，也就是說您不需要自己尋找硬體與設定測試 rig。這不須對負載測試作任何更動，因為它只是一個選擇雲端和內部部署的按鈕而已。選擇雲端代表您就可以選擇要使用哪個 Azure 數據中心作為負載來源：
這裡有一些關於雲端負載測試更詳細的說明，與一個 10 分鐘的影片。
最後，您可以從 Enterprise 的 MSDN 取得的額外好處（比起 Professional）：
您可以在這裡取得更多詳細的資訊。
希望這讓您初步地了解這些差異，而如果您正在決定要使用哪個版本或決定升級為 Enterprise，您都將可以對這些主要的額外功能有更多的了解。
本文翻譯自 6 differences between VS 2015 Enterprise and Pro
若對以上技術及產品有任何問題，很樂意為您服務! 請洽：台灣微軟開發工具服務窗口 – MSDNTW@microsoft.com / 02-3725-3888 #4922
Text version to copy
$arr $rootFolder $a $fileDate $outputFile $fileExtension
Get-ChildItem
}
|
お恥ずかしい話。うっかりものの私はインストール時に設定したパスワードを失念しちゃいました。
自分の手が覚えてそうなパスワードをランダムで実行するというクラックを何度か試みたのですが、自分って思ってたよりもセキュアらしくて結局パスワードを当てることはできませんでした(´・ω・｀)
いろいろなドキュメント探したのですが、ユーザーを追加しようにも、パスワード再設定しようにも管理者権限が無いと操作不能だったので、Windows Subsystem for Linux を再インストールすることぐらいしかできません。
今回は、Windows Subsystem for Linux の再インストールの手順について書いてみます。
Windows Subsystem for Linux を削除します。
lxrun /uninstall
Windows Subsystem for Linuxをインストールします。
lxrun /install
初回インストール時同様に、既定のUNIXユーザー名とパスワードをプロンプト画面で入力します。
本情報の内容（添付文書、リンク先などを含む）は、作成日時点でのものであり、予告なく変更される場合があります。
Wow! Peter has done everything! He’s been an MVP, Microsoft Partner, MCC, Microsoft employee, and Microsoft vendor! I’ll update this part in a bit and add some images. For now, let’s get to the interview!
Who are you, where are you, and what do you do? What are your specialty technologies?
I’m Peter Geelen, living in Leuven, Belgium. Consultant in Enterprise Security, Identity and Access management, managing consultant at Quest For Security.
Currently working as freelance contractor, with a long standing experience on Microsoft technologies, mainly on Identity manager (like FIM2010 and MIM2016, previously MIIS 2003, ILM 2007).
As Identity & Access management isn’t limited to particular technology, I’ve got quite some experience in helping and guiding customers on enterprise security, cybersecurity, implementing security policies, system hardening…
As MCT I enjoy teaching classes in these technologies.
What are your big projects right now?
I’m continuously working to stay on top with relevant certifications like CISA, CISSP, CISSP-ISSAP, CCSK and Microsoft certifications MCT, MCSA, MCP, MCTS, ..
Now working hard for ISC² trainer accreditation and planning for ISO27000 implementer and auditor certification.
Recently, I’ve been involved in review the fresh MIM 2016 handbook.
And, of course, Microsoft community, after hours.
What Microsoft Forums do you participate in? What different roles do you play?
You’ll see me on the Wiki forum and the FIM/MIM forum both as participant and as moderator, keeping the forums in good shape.
Also the MIMWAL forum, as moderator
In what other sites and communities do you contribute your technical knowledge?
Since a few years, I’m spending my after work time on the TechNet Wiki. Some accuse me of not sleeping (yes, true).
Already from the early start of the Wiki, I’ve been publishing articles on MS identity manager, (MIIS, ILM, FIM, and now MIM 2016). But you’ll also find content on other enterprise security platforms.
That’s from the perspective of MS technology platforms, but I’ve taken another important role on the TNWiki as administrator handling Wiki Governance and administration.
So you’ll find a lot of non-technical articles on the Wiki about the Wiki Governance. I try to maintain my activity log at the Wiki, so you can quickly get a list of my articles I’ve posted on the Wiki and blogs.
On what forum threads have you collaborated with other community members to help answer a question?
On Technology level, the FIM/MIM forum is my home base, not a specific thread but the forum as a whole.
The FIM community has been one of the first to jump on the TechNet Wiki when it started in 2010.
And, if you look the Wiki, many of the issues that initially got posted as questions on the Forum finally land on the TNWiki with a very decent quality of content. Furthermore we have some smart support team people like Tim Macaulay and David Steadman that are posting awesome support articles on Wiki. Which, in return is a great reference for the most common questions on the Forums. This is perfect example of how forums and Wiki complement each other.
Do you have any comments for product groups about the MSDN and TechNet Forums that they moderate?
For a long time spam and bulk posters are a plague on the forums.
I know that the teams are working constantly to keep the forums spam free, but not always with success… due to the sheer volume of posts. Currently the team is evaluating more advanced solutions to bring down the spam. But just realize this will be a continuous battle. Lots of people get fed up with the spam and don’t take time to report these spam posts on the forums. But you should, don’t ignore these spam posts.
The more people report the spam, the less work everyone has…
Please keep encouraging people to report spam.
Furthermore I’m absolutely in favor of using the reputation system in a smarter way.
Spam accounts have very typical behavior, zero points, large volume of posts, lots of URLs… as they want to get a high volume click rate on their posts.
I would like to suggest to moderate questions of people with a low reputation profile until a certain maturity is achieved.
People can achieve maturity by actively participating in the community (answering questions, engaging with some one elses questions, research options, provide suggestions…)
This is a signification difference with bots or spammers. We don’t need complex technical solutions to put a stop on the spam.
Do you have any tips for people asking questions on MSDN/TechNet Forums?
The key to success of getting useful answers is essentially in the way you ask questions: The smarter your question the better the answer. Sounds pretty normal and obvious, but if you’re question is wrong, it will take a lot of effort for your audience to help you…
The worst thing is to get answers you already know.
It’ essential to sketch the situation you’re in, provide some background. With some simple keywords you must be able to explain what the situation is.
Also very important is to explain, what investigations you have done yourself. (Step 1: RTFM) What options did you try already (or not)?
Formulate your key question very briefly.
Ask side questions later on, when your primary issue is solved.
For the FIM forum, I’ve collected some practical hints and tips in a Wiki article which has some downloadable versions at Gallery. Check it out: FIM/MIM Forum: How to get the maximum return on your forum question?
Do you have any tips for people answering questions on MSDN/TechNet Forums?
Do you have any tips for moderators of MSDN/TechNet Forums?
=================
Thank you Peter for your thousands of contributions to the community and to the forums! You’ve really been a huge team player and advocate for Microsoft technologies!
Please join me in thanking Peter Geelen!
May the Forums be with you (cheesy but painfully memorable),
– Ninja Ed
In this blog I am going to describe the setup required for automatic allocation examples that can be used within Budget Planning:
Budgeting> Setup> Budget Planning> Budget Planning Configuration> Allocation Schedules
Add
Allocation schedule: Distribute
Allocation method: Distribute
Source Scenario: Baseline
Destination Scenario: Baseline
Add
Allocation schedule: Copy Baseline to Forecasted
Allocation method: Allocate across periods
Period key: 40
Source Scenario: Baseline
Destination Scenario: Forecasted
Add
Allocation schedule: AggregateBaseline
Allocation method: Aggregate
Source Scenario: Baseline
Destination Scenario: Baseline
Add
Allocation schedule: AggregateForecasted
Allocation method: Aggregate
Source Scenario: Forecasted
Destination Scenario: Forecasted
Add
Allocation schedule: MonthlyBaseline
Allocation method: Allocate across periods
Period Key: Month
Source Scenario: Baseline
Destination Scenario: Baseline
Add
Budget planning workflow and stage: Parent workflow, Initial
Allocation Schedule: Distribute
Add
Budget planning workflow and stage: Child workflow, Submitted
Allocation Schedule: MonthlyBaseline
Add
Budget planning workflow and stage: Child workflow, Ready for approval
Allocation Schedule: Copy Baseline to Forecasted
Add
Budget planning workflow and stage: Parent workflow, CFO Review
Allocation Schedule: Aggregate Baseline
Add
Budget planning workflow and stage: Parent workflow, CFO Review
Allocation Schedule: Aggregate Forecasted
Parent Budget Plan with elements in the following order:
Start
Activate associated budget plan
Budget planning stage allocation
Review associated budget plan
Stage transition budget plan
Budget planning stage allocation
Review budget plan
End
Activate
Create new> Budget Plan workflows
Child Budget Plan with elements in the following order:
Start
Stage transition budget plan
Budget planning stage allocation
Review budget plan
Stage transition budget plan
Budget planning stage allocation
Review budget plan
Stage transition budget plan
End
Select the Budget Cycle, Ledger, Attachment Folder and Organization Hierarchy being used
In this example, Finance Department is the top of this Organization Hierarchy, thus will be assigned the Parent Workflow
All other Departments and Business Units are assigned the Child Workflow
With the Parent Workflow selected in the stage rules, the Initial and CFO review stages must have Associate budget plan, Add lines and Modify Lines selected, as well as a valid template assigned.
With the Child Workflow selected in the stage rules, the Distribute and Approved stages needs to have Associate budget plan, Add lines and Modify lines selected, as well as a valid template assigned.
The stages of Submitted and Ready for approval need to only have Add lines and Modify lines selected, as well as a valid template assigned.
Submit Parent Workflow
Complete the review stage and child budget plans are now approved with a document status of Finalized. 
Hello friends – It would be neglectful for the INT 3 blog to initialize without discussing the fundamental principles necessary to develop the reverse engineering mindset. Last month I spoke at an internal, biyearly Microsoft conference in Seattle. The talk focused on my experience debugging a troublesome z-order bug causing a logon window to disappear while users attempted to logon to a third-party application from their field locations. Debugging z-order issues is an ugly business. Before stepping the audience through the debugger output projected on the big screen in the session room, I asked the question, “where do you start debugging an issue when there is no error message generated, no crash dump created, no blocking threads to examine, no event log message logged, nor any ETW trace output generated? Where is the debugging entry point for an elusive disappearing logon window?”
The answer culminated into a discussion of the three “Reverse Engineering Principles” I have strived to cultivate over the last eighteen years. First I discussed the importance of building your reverse engineering toolbox by mastering tools such as Windbg, IDA Pro, debug extensions such as MEX, debug scripts, and the Sysinternals suite. We spent time discussing the importance of solid code comprehension skills which includes understanding language primitives, identifying design principles and possessing a familiarity with compiler specifics. Then I wrapped up by deliberating on the importance of having a reasonable level of architecture knowledge including both operating system and processor semantics. Growing in all three of these areas will continue to develop the reverse engineering mindset.
Over the next couple of months, I will unpack these principles in a ‘Reverse Engineering Principles’ series named REP for short. The series will be loaded with sample assembly snippets, C code examples and Windbg walkthroughs. The first REP article in the series will pay homage to Matt Pietrek’s ‘Under the Hood’ article from February of 1998 with extended register and assembly walk-throughs. You can also count on Trey and Dan to run concurrent series and articles discussing other topics.
If you’re curious about the debugging starting point for the disappearing logon window issue, knowing the GDI architecture and how WinEvents operate (e.g. REP Principle of Architecture Knowledge) pointed me to my debug entry point.
And one more thing before we part ways this week – I mentioned the MEX tool above. MEX is a newly released debug extension for Windbg sustained by my team. Our design goal is to make you ‘faster as a debugger’. Download MEX, load it into Windbg with the .load command and check it out.
-Ron
Since Windows 8, Microsoft moved makecert.exe from the Visual Studio installation to the Windows SDK. For Windows 10, get the SDK here.
Then open a developer command prompt and issue this command:
makecert.exe -sv myAzureAutomationCert.pvk -n "CN=My Azure Automation Certificate" myAzureAutomationCert.cer
Then in the Azure portal, use the instructions in this azure.com documentation page to finish the process.
Cheers!
Based on some questions I’ve been getting lately, it seems like now’s a good time to revisit my classic post Anatomy of Direct3D 11 Create Device updated for Direct3D 12!
The first thing to note is that while you can pass a nullptr for the ‘default’ device with Direct3D 12 to D3D12CreateDevice, that’s probably not the best solution. At this point, every driver on Windows 7 or later supports Direct3D 11, so you can pretty safely assume the default device is going to support Direct3D 11 at some Direct3D hardware feature level. While a lot of existing (as well as new) GPUs support Direct3D 12, this doesn’t apply to all GPUs. Specifically, a new WDDM 2 driver is required to support Direct3D 12, and there are no devices below Direct3D Feature Level 11.0 that are expected to get such updated drivers.
Another difference is that the debug device is not enabled through a creation flag like it is in Direct3D 12. Therefore, our first step is to enable debugging if available (the debug device is only present if the Graphics Tools Windows 10 optional feature is enabled). I’m making use of Microsoft::WRL::ComPtr which is recommended for both Direct3D 11 and Direct3D 12 (see this page for more information on this useful smart-pointer for COM programming).
No change period allocation – will be used to copy lines from one scenario to another
Add lines that include the dimensions used within the Organizational Hierarchy
#if defined(_DEBUG)
// Enable the debug layer.
{
ComPtr<ID3D12Debug> debugController;
if (SUCCEEDED(D3D12GetDebugInterface(IID_PPV_ARGS(&debugController))))
{
debugController->EnableDebugLayer();
}
}
#endifNext, we create a DXGI factory:
ComPtr<IDXGIFactory1> dxgiFactory;
HRESULT hr = CreateDXGIFactory1(IID_PPV_ARGS(&dxgiFactory));
if (FAILED(hr))
// Error!Then we scan DXGI adapters looking for one that supports Direct3D 12:
ComPtr<IDXGIAdapter1> adapter;
for (UINT adapterIndex = 0;
DXGI_ERROR_NOT_FOUND !=
dxgiFactory->EnumAdapters1(adapterIndex, &adapter);
++adapterIndex)
{
DXGI_ADAPTER_DESC1 desc;
hr = adapter->GetDesc1(&desc);
if (FAILED(hr))
continue;
if (desc.Flags & DXGI_ADAPTER_FLAG_SOFTWARE)
{
// Don't select the Basic Render Driver adapter.
continue;
}
// Check to see if the adapter supports Direct3D 12,
// but don't create the actual device yet.
if (SUCCEEDED(
D3D12CreateDevice(adapter.Get(), D3D_FEATURE_LEVEL_11_0,
_uuidof(ID3D12Device), nullptr)))
{
break;
}
}Note: We are excluding the Microsoft Basic Render adapter here (aka WARP+VGA driver) since games typically don’t play well using WARP, but keep in mind that WARP12 is not present on standard Windows 10 systems; it’s only installed as part of the Graphics Tools optional feature.
If there’s no Direct3D 12-capable hardware, then for development builds it is useful to fallback to the WARP software device for Direct3D 12. Here is another difference compared to Direct3D 11: WARP12 is a specific adapter you obtain from the DXGI factory:
#if !defined(NDEBUG)
if (!adapter)
{
ComPtr<IDXGIFactory4> dxgiFactory4;
if (SUCCEEDED(dxgiFactory.As(&dxgiFactory4)))
{
if (FAILED(dxgiFactory4->EnumWarpAdapter(IID_PPV_ARGS(&adapter))))
{
adapter.Reset();
}
}
}
#endifIf at this point, we still don’t have a valid adapter, then either a fatal error should be displayed, -or- if the application supports it, you should fall back to using Direct3D 11.
Otherwise, it’s time to create the device. Here’s another Direct3D 11 difference: Instead of providing an input array of every possible Direct3D feature level your application supports, you simply provide the minimum feature level you can use. Because as I noted above there’s no expected drivers for anything below Feature Level 11.0, that’s the minimum I’m using in this code and you’ll find the same in the Visual Studio DirectX 12 templates.
ComPtr<ID3D12Device> device;
hr = D3D12CreateDevice(adapter.Get(),
D3D_FEATURE_LEVEL_11_0, IID_PPV_ARGS(&device));
if (FAILED(hr))
// Error!Great, so we have a device, but how do you know if you managed to get a higher feature level than your minimum? Here we use CheckFeatureSupport to find that out:
static const D3D_FEATURE_LEVEL s_featureLevels[] =
{
D3D_FEATURE_LEVEL_12_1,
D3D_FEATURE_LEVEL_12_0,
D3D_FEATURE_LEVEL_11_1,
D3D_FEATURE_LEVEL_11_0,
};
D3D12_FEATURE_DATA_FEATURE_LEVELS featLevels =
{
_countof(s_featureLevels), s_featureLevels, D3D_FEATURE_LEVEL_11_0
};
D3D_FEATURE_LEVEL featureLevel = D3D_FEATURE_LEVEL_11_0;
hr = device->CheckFeatureSupport(D3D12_FEATURE_FEATURE_LEVELS,&featLevels, sizeof(featLevels));
if (SUCCEEDED(hr))
{
featureLevel = featLevels.MaxSupportedFeatureLevel;
}At this point, you are ready to create the swap chain. For Win32 classic desktop apps you use CreateSwapChainForHwnd, and for Universal Windows Platform (UWP) apps you use CreateSwapChainForCoreWindow, both of which require IDXGIFactory2 or later:
ComPtr<IDXGIFactory2> dxgiFactory2;
if (FAILED(dxgiFactory.As(&dxgiFactory2)))
// Fatal error (shouldn't happen in practice at this point)The key thing to note about swap chain creation is that you must use either DXGI_SWAP_EFFECT_FLIP_SEQUENTIAL or DXGI_SWAP_EFFECT_FLIP_DISCARD for the DXGI_SWAP_CHAIN_DESC1.SwapEffect because the older swap effects are not supported for Direct3D 12. For Universal Windows Platform (UWP) apps, you should also consider using DXGI_SCALING_ASPECT_RATIO_STRETCH for the DXGI_SWAP_CHAIN_DESC1.Scaling, but for Win32 classic desktop swap chains you need to stick with DXGI_SCALING_NONE or DXGI_SCALING_STRETCH.
To build an application using Direct3D 12 APIs, you must make use of the Windows 10 SDK. The latest version is the Windows 10 Anniversary Update SDK (14393). With Visual Studio 2015, you install it via a custom install option and for Win32 classic desktop projects you’ll need to explicitly change the project property to use it rather than the default Windows 8.1 SDK (Spring 2015).
With the Windows 10 Anniversary Update, newer drivers and devices can support some additional features for Direct3D 12. You can obtain the 12.1 interface from your 12.0 device by using QueryInterface or ComPtr::As–this will fail on older versions of Windows 10.
ComPtr<ID3D12Device1> device1;
if (SUCCEEDED(device.As(&device1)))
{
// Direct3D 12.1 Runtime is available
}If your application supports Windows 8.1 or earlier, then you need to make use of explicit rather than implicit linking to the Direct3D 12 functions since they are not available before Windows 10. Implicit linking to dxgi.lib (and d3d11.lib if needed) is not a problem unless you are trying to support Windows XP as well. The code above is careful to try to use DXGI 1.1 for the initial detection to support Windows 7 systems.
HMODULE dx12 = LoadLibraryEx(L"d3d12.dll",
nullptr, LOAD_LIBRARY_SEARCH_SYSTEM32);
if (!dx12)
// Fallback to using Direct3D 11
auto pD3D12CreateDevice = reinterpret_cast<PFN_D3D12_CREATE_DEVICE>(
GetProcAddress(dx12, "D3D12CreateDevice"));
if (!pD3D12CreateDevice)
// Fallback to using Direct3D 11
...
#if defined(_DEBUG)
// Enable the debug layer.
auto pD3D12GetDebugInterface =
reinterpret_cast<PFN_D3D12_GET_DEBUG_INTERFACE>(
GetProcAddress(dx12, "D3D12GetDebugInterface"));
if (pD3D12GetDebugInterface)
{
ComPtr<ID3D12Debug> debugController;
if (SUCCEEDED(pD3D12GetDebugInterface(
IID_PPV_ARGS(&debugController))))
{
debugController->EnableDebugLayer();
}
}
#endif
...
// Change both cases where we use D3D12CreateDevice above to
// pD3D12CreateDevice. If you fail to find an adapter, use
// Direct3D 11 instead
Because the minimum OS version is enforced for the platform, you can count on IDXGIFactory4 always being available to you can simplify the code above by starting out with it which is what you’ll find in the Visual Studio DirectX 12 templates:
ComPtr<IDXGIFactory4> dxgiFactory;
HRESULT hr = CreateDXGIFactory1(IID_PPV_ARGS(&dxgiFactory));
if (FAILED(hr))
// Error!Related:Direct3D Game Visual Studio templates (Redux), DirectX Tool Kit for DirectX 12
当社では、 Surface Pro 4 / Surface Book 専用の新機能として、”Microsoft Surface Enterprise Management Mode (SEMM)” を公開いたしました。
これは、管理者が指定した UEFI の設定（内蔵デバイスの無効化など）を Surface 端末に展開するための機能で、多数の端末に同じ設定を適用することが容易になります。
以下の TechNet ページにてご利用方法を解説しておりますが、現時点で英語版のみとなるため、本記事にてポイントをご紹介します。
Microsoft Surface Enterprise Management Mode
SEMM の機能を利用して UEFI 設定を展開するには、”Microsoft Surface UEFI Configurator” という専用のツールを利用して “Configuration Package” （設定を保存したインストーラー パッケージ）を作成し、それを各端末に適用します。
手順は以下のようになります。
これで、設定対象の Surface は指定した UEFI 設定が適用された状態になります。
このほか、 SEMM の機能には、UEFI設定の解除や緊急時の回復があります。詳細は原文サイトをご参照ください。
テスト用の証明書ファイルを出力するには、以下のテキストを .ps1 拡張子で保存し、 PowerShell スクリプトとして実行します。
実行すると、%WINDIR%system32 に TempOwner.pfx という証明書ファイルが出力されます。テスト用の証明書ファイルのパスワードは “12345678” です。
—————————————————————————–
if (-not (Test-Path “Demo Certificate”)) { New-Item -ItemType Directory -Force -Path “Demo Certificate” }
if (Test-Path “Demo CertificateTempOwner.pfx”) { Remove-Item “Demo CertificateTempOwner.pfx” }
# Generate the Ownership private signing key with password 12345678
$pw = ConvertTo-SecureString “12345678” -AsPlainText -Force
$TestUefiV2 = New-SelfSignedCertificate `
-Subject “CN=Surface Demo Kit, O=Contoso Corporation, C=US” `
-Type SSLServerAuthentication `
-HashAlgorithm sha256 `
-KeyAlgorithm RSA `
-KeyLength 2048 `
-KeyUsage KeyEncipherment `
-KeyUsageProperty All `
-Provider “Microsoft Enhanced RSA and AES Cryptographic Provider” `
-NotAfter (Get-Date).AddYears(25) `
-TextExtension @(“2.5.29.37={text}1.2.840.113549.1.1.1”) `
-KeyExportPolicy Exportable
$TestUefiV2 | Export-PfxCertificate -Password $pw -FilePath “Demo CertificateTempOwner.pfx”
—————————————————————————–
The Microsoft Dynamics Lifecycle Services team is happy to announce the immediate availability of Dynamics AX Platform version 7.2 (August 2016).
NEW FEATURES
Dynamics AX Platform version 7.2 (August 2016) is now available
Starting today you can deploy Dynamics AX Platform version 7.2 from LCS. Platform version 7.2 will be deployed using Azure Resource Manager technology (ARM) therefore, you will have to set up LCS Azure connectors which are ARM enabled. You can find details on how to set up ARM enabled connectors in the wiki topic, Azure Resource Manager onboarding (http://ax.help.dynamics.com/en/wiki/arm-onboarding/).
In the Partner project workspace, after you select the topology you want to deploy, you can select from RTW, May 2016 Update (Update 1), or August 2016 Update (Update 2).
To learn more about what’s new in this release, see What’s new or changed in Dynamics AX platform version 7.2 (August 2016).
In the Implementation project, after you click Configure, you will be provided with an option to choose from RTW, May 2016 Update (Update 1), or August 2016 Update (Update 2).
If you want to deploy the most recent platform update, select Dynamics AX – Develop (August 2016 Update), as shown below.
This will load a specific deployment configuration screen for you.
You can also update your existing environments to the new Dynamics AX platform. The package is available in the Shared Asset Library in LCS, accessed by the tile on the main LCS landing page. Instructions for deploying this package are available here.
Code Upgrade Tool
The LCS code upgrade tool will now upgrade your Dynamics AX source code and metadata to the latest platform update, Dynamics AX Platform version 7.2 (August 2016), and the latest application update (May 2016).
Update Experience:
Customers on Dynamics AX Platform version 7.2 (August 2016) will see relevant updates/hotfixes on their platform environment. The experience will be same as the May 2016 update experience.
Serviceability
Customers and partners will be able to update their environments (Demo, Sandbox, and Production) with customizations and hotfixes directly through LCS without having to remote into any environment to run through the update steps manually. On the Demo and Sandbox environments, this flow is self-serve and you can automatically apply updates through LCS; while Production LCS provides a flow to submit a request to apply package through LCS and Microsoft Service Engineering team is responsible for applying the update. For more information, see the wiki topic, Apply a deployable package on a Dynamics AX system (https://ax.help.dynamics.com/en/wiki/apply-a-deployable-package-on-a-dynamics-ax-system/).
Telemetry Monitoring and Diagnostics
Customers and partners can perform advanced SQL diagnostics using the SQL Now and Index Usage tools added in LCS. The SQL Now feature gives the ability to troubleshoot SQL issues in real time by looking into what queries are blocked and which queries are blocking them. It also provides a view in tables that have locks on them. The Index Usage view shows the most expensive indices on the environment based on seeks vs. scans along tables with the highest row count.
が
