This document summarizes a webinar on minimizing the impact of the October 2015 Patch Tuesday. It discusses the Microsoft, Adobe, and Google security bulletins released, including fixes for remote code execution, elevation of privilege, and information disclosure vulnerabilities. It provides an overview of the affected products and vulnerabilities addressed. It also reviews other patches released since the previous Patch Tuesday and lists resources for further information.
The document outlines the key details of patches released during the November 2015 Patch Tuesday, including 12 Microsoft security bulletins addressing 53 vulnerabilities, an Adobe Flash Player bulletin addressing 17 vulnerabilities, and a Google Chrome release addressing 1 vulnerability and the 17 Flash Player issues. Major products affected include Windows, Internet Explorer, Edge, Office, Flash Player and Google Chrome. The document provides information on the security impacts of each patch and any known issues.
инструкции и утилиты для удаления остатков антивирусных программbelhonka
This document provides instructions and removal tools for uninstalling various antivirus and security software programs. It lists over 70 different antivirus products from vendors such as Avast, AVG, Avira, BitDefender, ESET, F-Secure, Kaspersky, McAfee, Microsoft, Sophos, Symantec and more. For each product, it specifies the supported Windows operating systems and provides a download link to the official uninstallation tool or a third party removal utility. The purpose is to completely remove all traces of the program from the system.
This document summarizes the October 2016 Patch Tuesday updates from Microsoft. It provides information on 42 security updates affecting Windows 10, Edge, Internet Explorer, and other Microsoft products. The updates fix critical vulnerabilities that could allow remote code execution or elevation of privilege. Administrators are advised to apply all security updates as soon as possible to protect systems.
This document summarizes the September 2016 Patch Tuesday webinar. It includes an agenda covering the monthly patch overview, known issues, bulletins, and Q&A. Details are provided on several security updates from Microsoft addressing vulnerabilities in Windows, Edge, Internet Explorer, Office, Exchange, and third party software. Recommendations are made around timely patching within 2 weeks to reduce exposure to exploited vulnerabilities.
Weather Forecast for Today? Advert Flood Coming from EastAVG Technologies
This document provides a technical analysis of a malware campaign spreading via a weather forecast application. It describes how the malware is spread, installed, and how it infects browsers to inject advertisements. The malware installs additional components that periodically download more ads without user notification for profit. It checks for virtual machines, extracts files from its resources, registers components to run automatically, and reports back infected system details for monitoring. The malware injects ads into Internet Explorer, Firefox, and Chrome by installing browser helper objects and add-ons.
Are you feeling like you'd like to have poked your fingers into the center of the Meltdown and Spectre patches like a box of Valentine's chocolates? There were some unsavory surprises for sure. Fortunately, the kinks are largely worked out and February Patch Tuesday is more straightforward. If there is one word for this month in patching, it's not "love" or "romance" but "privilege." Patch the elevation-of-privilege vulnerabilities, and then take a closer look at your policy on privilege management. Make sure you're keeping attackers from storming the heart of your organization.
This document summarizes the November 2016 Patch Tuesday updates from Microsoft. It provides an overview of key bulletins addressing vulnerabilities in Windows 10, Edge, Internet Explorer, and other Microsoft products. Notably, it fixes 73 vulnerabilities in Windows 10 and 39 vulnerabilities in other supported Windows versions. It also includes an Adobe Flash Player update fixing 9 vulnerabilities. The updates require restarts and range from critical remote code execution fixes to important privilege escalation issues.
This document summarizes a webinar on minimizing the impact of the October 2015 Patch Tuesday. It discusses the Microsoft, Adobe, and Google security bulletins released, including fixes for remote code execution, elevation of privilege, and information disclosure vulnerabilities. It provides an overview of the affected products and vulnerabilities addressed. It also reviews other patches released since the previous Patch Tuesday and lists resources for further information.
The document outlines the key details of patches released during the November 2015 Patch Tuesday, including 12 Microsoft security bulletins addressing 53 vulnerabilities, an Adobe Flash Player bulletin addressing 17 vulnerabilities, and a Google Chrome release addressing 1 vulnerability and the 17 Flash Player issues. Major products affected include Windows, Internet Explorer, Edge, Office, Flash Player and Google Chrome. The document provides information on the security impacts of each patch and any known issues.
инструкции и утилиты для удаления остатков антивирусных программbelhonka
This document provides instructions and removal tools for uninstalling various antivirus and security software programs. It lists over 70 different antivirus products from vendors such as Avast, AVG, Avira, BitDefender, ESET, F-Secure, Kaspersky, McAfee, Microsoft, Sophos, Symantec and more. For each product, it specifies the supported Windows operating systems and provides a download link to the official uninstallation tool or a third party removal utility. The purpose is to completely remove all traces of the program from the system.
This document summarizes the October 2016 Patch Tuesday updates from Microsoft. It provides information on 42 security updates affecting Windows 10, Edge, Internet Explorer, and other Microsoft products. The updates fix critical vulnerabilities that could allow remote code execution or elevation of privilege. Administrators are advised to apply all security updates as soon as possible to protect systems.
This document summarizes the September 2016 Patch Tuesday webinar. It includes an agenda covering the monthly patch overview, known issues, bulletins, and Q&A. Details are provided on several security updates from Microsoft addressing vulnerabilities in Windows, Edge, Internet Explorer, Office, Exchange, and third party software. Recommendations are made around timely patching within 2 weeks to reduce exposure to exploited vulnerabilities.
Weather Forecast for Today? Advert Flood Coming from EastAVG Technologies
This document provides a technical analysis of a malware campaign spreading via a weather forecast application. It describes how the malware is spread, installed, and how it infects browsers to inject advertisements. The malware installs additional components that periodically download more ads without user notification for profit. It checks for virtual machines, extracts files from its resources, registers components to run automatically, and reports back infected system details for monitoring. The malware injects ads into Internet Explorer, Firefox, and Chrome by installing browser helper objects and add-ons.
Are you feeling like you'd like to have poked your fingers into the center of the Meltdown and Spectre patches like a box of Valentine's chocolates? There were some unsavory surprises for sure. Fortunately, the kinks are largely worked out and February Patch Tuesday is more straightforward. If there is one word for this month in patching, it's not "love" or "romance" but "privilege." Patch the elevation-of-privilege vulnerabilities, and then take a closer look at your policy on privilege management. Make sure you're keeping attackers from storming the heart of your organization.
This document summarizes the November 2016 Patch Tuesday updates from Microsoft. It provides an overview of key bulletins addressing vulnerabilities in Windows 10, Edge, Internet Explorer, and other Microsoft products. Notably, it fixes 73 vulnerabilities in Windows 10 and 39 vulnerabilities in other supported Windows versions. It also includes an Adobe Flash Player update fixing 9 vulnerabilities. The updates require restarts and range from critical remote code execution fixes to important privilege escalation issues.
It’s 2018, we’re resolved to help you secure your systems against whatever the new year brings, and January Patch Tuesday is bringing it! This month’s updates include a fix for a known Office exploit and a host of patches to tackle the Meltdown and Spectre vulnerabilities. About that last bit, though, take note: there is no known malicious use of these vulnerabilities to date. Take the time you need now to put the patches through their paces and get them in place, because this security issue is likely to tempt the bad guys.
This document summarizes a webinar about minimizing the impact of the December 2015 Patch Tuesday updates. It includes an overview of the Microsoft and third party patches released, including 12 Microsoft security bulletins addressing 71 vulnerabilities and an Adobe Flash Player bulletin addressing 78 vulnerabilities. It also provides details on some of the most critical patches, including patches addressing remote code execution vulnerabilities in Windows 10, Internet Explorer, Edge, and other Microsoft products. The webinar aims to help organizations understand and address the patches.
This document summarizes a webinar on the December 2016 Patch Tuesday updates. It provides an agenda for the webinar including an overview of the December patches, known issues, and bulletins. It then lists details on several Microsoft and Adobe security updates released on Patch Tuesday, including the impacted products, descriptions of the vulnerabilities fixed, severity ratings, and whether a restart is required.
This document summarizes the July 2015 Patch Tuesday updates from Microsoft, Adobe, Oracle, and Google. It provides an overview of the security bulletins and vulnerabilities addressed, including 14 Microsoft bulletins addressing 59 vulnerabilities, with 5 rated critical and 9 rated important. It also summarizes updates from Adobe (Flash, Acrobat, Shockwave), Oracle Java, and Google Chrome, noting the products affected and vulnerabilities fixed in each update.
This document summarizes a webinar about the January 2016 Patch Tuesday updates. It includes:
- An agenda for the webinar covering the January Patch Tuesday overview, known issues, bulletins, and Q&A.
- Summaries of several Microsoft security bulletins addressing vulnerabilities in Windows 10, Edge, Internet Explorer, Office, and other Microsoft products. It also summarizes updates from Adobe for Flash Player, Acrobat, and Reader.
- Information about other industry news items like the end of support for some Windows versions and changes to Flash redistribution requirements.
- Cause you aren't ready for 101.
These are the slides I used for my RailsConf 2019 workshop. It contains the lecture and some of the exercises from the workshop, although obviously it's meant to be done in person.
This document summarizes the September 2015 Patch Tuesday updates from Microsoft and other vendors. It provides an overview of the 56 vulnerabilities addressed by Microsoft across 12 security bulletins, including which products are affected and the impact of the vulnerabilities. It also summarizes the 2 vulnerabilities addressed in the Adobe Shockwave bulletin. The document recommends applying all patches and offers to answer any questions.
Around the globe, Halloween and related celebrations are right around the corner. In the states, this is the month of trick-or-treat and pumpkin patches. And out in Redmond, Washington, Microsoft is focused on patches of a different sort—keeping an eye on vulnerabilities hackers could use to unleash nasty tricks upon the world. For October Patch Tuesday you’d be wise to patch all Microsoft CVEs swiftly, publicly disclosed and otherwise, before more than just the one we’ve noted below get exploited.
The document summarizes an upcoming webinar on the August 2018 Patch Tuesday updates. The webinar will include an overview of the August patches, discussion of notable security news items, and a review of Microsoft and third-party bulletins. It will also cover Windows lifecycle awareness, new patch notification systems, and known issues for some of the August updates. Attendees can ask questions during the live Q&A portion.
Java Insecurity: How to Deal with the Constant VulnerabilitiesLumension
Just over a decade ago, the outcry over Microsoft’s security problems reached such a deafening level that it finally got the attention of Bill Gates, who wrote the famous Trustworthy Computing memo. Today, many would say that Microsoft leads the industry in security and vulnerability handling.
Now, it’s Java that’s causing the uproar. But has Oracle learned anything from Microsoft in handling these seemingly ceaseless problems? I’ll start by reviewing the wide-ranging Java security changes Oracle is promising to make. They sound so much like the improvements Microsoft made back with Trustworthy Computing that I’m amazed it hasn’t been done before! We’ll move on to discuss what you can do now to address Java security in your environment.
One of the banes of security with Java is the presence of multiple versions of Java, often on the same computer. Sometimes you really need multiple versions of Java to support applications with version dependencies (crazy, I know). But other times, multiple copies of Java are there “just because.” In this webinar, we’ll talk about the current Java mess and how you can get out of it, including:
Assessment. We’ll discuss ways and tools for cataloging what versions of Java are actually out there on your endpoints.
Identification. We’ll look at methods for identifying which versions are actually required by your users; for instance, I’ll show you how you might use Process Tracking and File Access events in the Windows Security Log to see which Java files are being accessed, by whom, and by which programs.
Disabling. Can you just disable Java? Maybe not for everyone, but what if you could disable it for certain roles within your company that make up 25% – or even 75% – of your workforce? That would be worth it. We’ll explore how you might go about such a measure.
Hardening. We’ll dive into the technical details of hardening Java and reducing your Java attack surface, where possible.
Filtering. Another way to reduce your Java risk is by filtering Java content at your gateway. Again not full coverage control – but what is?
Patching. Then, we’ll delve into the Java patching nightmare. Depending on self-updaters on each endpoint, is could be a recipe for disaster, and I’ll explain why. Basically the only way out of the Java mess is a 3rd party solution that can perform centralized patch management and remediation and that’s where our sponsor, Lumension, will come in.
This document provides a summary of key Volatility plugins and memory analysis steps. It outlines plugins for identifying rogue processes, analyzing process DLLs and handles, reviewing network artifacts, checking for code injection evidence, looking for rootkit signs, and dumping suspicious processes/drivers. The document also provides information on memory acquisition, converting hibernation files and dumps, artifact timelining, and registry analysis plugins.
The holidays are just around the corner. How, you wonder, are we going to tie those into November Patch Tuesday? Through tradition, of course! Because what are the holidays without that treasured recipe you replicate line by line each year? And what is security without steadfast adherence to the list of controls you've put in place? The KRACK vulnerability is another in this year's endless litany of reminders that keeping up with software updates is critical. Be sure you've pushed out the October OS updates - and don't let the tradition slip this month either, as there are quite a few Critical security vulnerabilities to patch.
This document summarizes an upcoming webinar about the August 2016 Patch Tuesday. The webinar will provide an overview of the patches released on Patch Tuesday, including known issues. It will discuss the bulletins and vulnerabilities addressed. There will be a question and answer session. The document reviews best practices for patch management and discusses specific bulletins and vulnerabilities in detail. It also lists security updates released between Patch Tuesdays.
This document summarizes Microsoft's August 2015 Patch Tuesday updates. It describes 14 Microsoft security bulletins addressing 58 vulnerabilities, an Adobe Flash bulletin addressing 35 vulnerabilities, and updates from Google Chrome and Mozilla Firefox. The updates resolve issues including remote code execution, elevation of privilege, and information disclosure. It provides details on the affected products and recommends applying all updates.
Security of Windows 10 IoT Core(FFRI Monthly Research 201506)FFRI, Inc.
•Windows 10 IoT is successor platform of Windows Embedded that optimized for embedded devices.
•Windows 10 IoT Core Insider Preview has been provided for single-board computers such as the Raspberry Pi 2.
•We show tutorial about security of Windows 10 IoT Core using the Raspberry Pi 2.
This document summarizes an upcoming webinar on the June 2016 Patch Tuesday. The webinar will provide an overview of the known issues and bulletins for June's Patch Tuesday, including updates for Windows 10, Internet Explorer, Edge, Office, Adobe Flash Player, and other Microsoft products. It lists the vulnerabilities addressed and their potential impacts, such as remote code execution or elevation of privilege. Attendees will have a chance to ask questions.
Introducing Intelligence Into Your Malware AnalysisBrian Baskin
With malware becoming more prevalent, and the pool of capable reversers falling short of overall need, there is a greater need to provide quick and efficient malware analysis for network defense. While many analysts have a grasp on how to appropriately reverse malware, there is large room for improvement by extracting critical indicators, correlating on key details, and cataloging artifacts in a way to improve your corporate response for the next attack. This talk will cover beyond the basics of malware analysis and focus on critical indicators that should analysts should focus on for attribution and better reporting.
Discover what’s new in Windows 8.1 regarding interface, settings, deployment, security, … How will Windows 8.1 fit in your enterprise? How do you upgrade? All answers are here!
This document provides an overview and demonstration of the Microsoft Web Platform tools: IIS Web Eco-System, Web Platform Installer (Web PI), and Web Deploy. The presentation covers the main components and features of each tool, how they work, and examples of common usage scenarios. Web PI simplifies installation of web software. Web Deploy enables deployment and synchronization of websites, applications, and databases between IIS servers. Usage scenarios demonstrated include synchronization, migration, packaging, and modifying sync behavior with rules.
- InstallAware is a software that simplifies the creation of Windows installer packages by abstracting the complexities of Windows Installer technology. It allows developers to build installers using a simple scripting language called MSIcode instead of programming custom actions.
- InstallAware can reduce the size of installer packages by up to 67% using advanced compression techniques. It also makes it easy to deploy runtime dependencies and optional application features on demand.
- In addition to simplifying installer authoring, InstallAware provides features to help developers manage customer relationships, consolidate multiple product editions into a single installer, and perform web-based software updates.
The document outlines the agenda and topics that will be covered in a training on MSI/Windows Installer for NGN. It includes an introduction, overview of legacy installers vs Windows Installer, details on key concepts like packages, products, components, features, properties, and more. It also discusses ICE validation, caching, rights management, and versions. The training will cover tools like AdminStudio and installing/configuring common applications.
It’s 2018, we’re resolved to help you secure your systems against whatever the new year brings, and January Patch Tuesday is bringing it! This month’s updates include a fix for a known Office exploit and a host of patches to tackle the Meltdown and Spectre vulnerabilities. About that last bit, though, take note: there is no known malicious use of these vulnerabilities to date. Take the time you need now to put the patches through their paces and get them in place, because this security issue is likely to tempt the bad guys.
This document summarizes a webinar about minimizing the impact of the December 2015 Patch Tuesday updates. It includes an overview of the Microsoft and third party patches released, including 12 Microsoft security bulletins addressing 71 vulnerabilities and an Adobe Flash Player bulletin addressing 78 vulnerabilities. It also provides details on some of the most critical patches, including patches addressing remote code execution vulnerabilities in Windows 10, Internet Explorer, Edge, and other Microsoft products. The webinar aims to help organizations understand and address the patches.
This document summarizes a webinar on the December 2016 Patch Tuesday updates. It provides an agenda for the webinar including an overview of the December patches, known issues, and bulletins. It then lists details on several Microsoft and Adobe security updates released on Patch Tuesday, including the impacted products, descriptions of the vulnerabilities fixed, severity ratings, and whether a restart is required.
This document summarizes the July 2015 Patch Tuesday updates from Microsoft, Adobe, Oracle, and Google. It provides an overview of the security bulletins and vulnerabilities addressed, including 14 Microsoft bulletins addressing 59 vulnerabilities, with 5 rated critical and 9 rated important. It also summarizes updates from Adobe (Flash, Acrobat, Shockwave), Oracle Java, and Google Chrome, noting the products affected and vulnerabilities fixed in each update.
This document summarizes a webinar about the January 2016 Patch Tuesday updates. It includes:
- An agenda for the webinar covering the January Patch Tuesday overview, known issues, bulletins, and Q&A.
- Summaries of several Microsoft security bulletins addressing vulnerabilities in Windows 10, Edge, Internet Explorer, Office, and other Microsoft products. It also summarizes updates from Adobe for Flash Player, Acrobat, and Reader.
- Information about other industry news items like the end of support for some Windows versions and changes to Flash redistribution requirements.
- Cause you aren't ready for 101.
These are the slides I used for my RailsConf 2019 workshop. It contains the lecture and some of the exercises from the workshop, although obviously it's meant to be done in person.
This document summarizes the September 2015 Patch Tuesday updates from Microsoft and other vendors. It provides an overview of the 56 vulnerabilities addressed by Microsoft across 12 security bulletins, including which products are affected and the impact of the vulnerabilities. It also summarizes the 2 vulnerabilities addressed in the Adobe Shockwave bulletin. The document recommends applying all patches and offers to answer any questions.
Around the globe, Halloween and related celebrations are right around the corner. In the states, this is the month of trick-or-treat and pumpkin patches. And out in Redmond, Washington, Microsoft is focused on patches of a different sort—keeping an eye on vulnerabilities hackers could use to unleash nasty tricks upon the world. For October Patch Tuesday you’d be wise to patch all Microsoft CVEs swiftly, publicly disclosed and otherwise, before more than just the one we’ve noted below get exploited.
The document summarizes an upcoming webinar on the August 2018 Patch Tuesday updates. The webinar will include an overview of the August patches, discussion of notable security news items, and a review of Microsoft and third-party bulletins. It will also cover Windows lifecycle awareness, new patch notification systems, and known issues for some of the August updates. Attendees can ask questions during the live Q&A portion.
Java Insecurity: How to Deal with the Constant VulnerabilitiesLumension
Just over a decade ago, the outcry over Microsoft’s security problems reached such a deafening level that it finally got the attention of Bill Gates, who wrote the famous Trustworthy Computing memo. Today, many would say that Microsoft leads the industry in security and vulnerability handling.
Now, it’s Java that’s causing the uproar. But has Oracle learned anything from Microsoft in handling these seemingly ceaseless problems? I’ll start by reviewing the wide-ranging Java security changes Oracle is promising to make. They sound so much like the improvements Microsoft made back with Trustworthy Computing that I’m amazed it hasn’t been done before! We’ll move on to discuss what you can do now to address Java security in your environment.
One of the banes of security with Java is the presence of multiple versions of Java, often on the same computer. Sometimes you really need multiple versions of Java to support applications with version dependencies (crazy, I know). But other times, multiple copies of Java are there “just because.” In this webinar, we’ll talk about the current Java mess and how you can get out of it, including:
Assessment. We’ll discuss ways and tools for cataloging what versions of Java are actually out there on your endpoints.
Identification. We’ll look at methods for identifying which versions are actually required by your users; for instance, I’ll show you how you might use Process Tracking and File Access events in the Windows Security Log to see which Java files are being accessed, by whom, and by which programs.
Disabling. Can you just disable Java? Maybe not for everyone, but what if you could disable it for certain roles within your company that make up 25% – or even 75% – of your workforce? That would be worth it. We’ll explore how you might go about such a measure.
Hardening. We’ll dive into the technical details of hardening Java and reducing your Java attack surface, where possible.
Filtering. Another way to reduce your Java risk is by filtering Java content at your gateway. Again not full coverage control – but what is?
Patching. Then, we’ll delve into the Java patching nightmare. Depending on self-updaters on each endpoint, is could be a recipe for disaster, and I’ll explain why. Basically the only way out of the Java mess is a 3rd party solution that can perform centralized patch management and remediation and that’s where our sponsor, Lumension, will come in.
This document provides a summary of key Volatility plugins and memory analysis steps. It outlines plugins for identifying rogue processes, analyzing process DLLs and handles, reviewing network artifacts, checking for code injection evidence, looking for rootkit signs, and dumping suspicious processes/drivers. The document also provides information on memory acquisition, converting hibernation files and dumps, artifact timelining, and registry analysis plugins.
The holidays are just around the corner. How, you wonder, are we going to tie those into November Patch Tuesday? Through tradition, of course! Because what are the holidays without that treasured recipe you replicate line by line each year? And what is security without steadfast adherence to the list of controls you've put in place? The KRACK vulnerability is another in this year's endless litany of reminders that keeping up with software updates is critical. Be sure you've pushed out the October OS updates - and don't let the tradition slip this month either, as there are quite a few Critical security vulnerabilities to patch.
This document summarizes an upcoming webinar about the August 2016 Patch Tuesday. The webinar will provide an overview of the patches released on Patch Tuesday, including known issues. It will discuss the bulletins and vulnerabilities addressed. There will be a question and answer session. The document reviews best practices for patch management and discusses specific bulletins and vulnerabilities in detail. It also lists security updates released between Patch Tuesdays.
This document summarizes Microsoft's August 2015 Patch Tuesday updates. It describes 14 Microsoft security bulletins addressing 58 vulnerabilities, an Adobe Flash bulletin addressing 35 vulnerabilities, and updates from Google Chrome and Mozilla Firefox. The updates resolve issues including remote code execution, elevation of privilege, and information disclosure. It provides details on the affected products and recommends applying all updates.
Security of Windows 10 IoT Core(FFRI Monthly Research 201506)FFRI, Inc.
•Windows 10 IoT is successor platform of Windows Embedded that optimized for embedded devices.
•Windows 10 IoT Core Insider Preview has been provided for single-board computers such as the Raspberry Pi 2.
•We show tutorial about security of Windows 10 IoT Core using the Raspberry Pi 2.
This document summarizes an upcoming webinar on the June 2016 Patch Tuesday. The webinar will provide an overview of the known issues and bulletins for June's Patch Tuesday, including updates for Windows 10, Internet Explorer, Edge, Office, Adobe Flash Player, and other Microsoft products. It lists the vulnerabilities addressed and their potential impacts, such as remote code execution or elevation of privilege. Attendees will have a chance to ask questions.
Introducing Intelligence Into Your Malware AnalysisBrian Baskin
With malware becoming more prevalent, and the pool of capable reversers falling short of overall need, there is a greater need to provide quick and efficient malware analysis for network defense. While many analysts have a grasp on how to appropriately reverse malware, there is large room for improvement by extracting critical indicators, correlating on key details, and cataloging artifacts in a way to improve your corporate response for the next attack. This talk will cover beyond the basics of malware analysis and focus on critical indicators that should analysts should focus on for attribution and better reporting.
Discover what’s new in Windows 8.1 regarding interface, settings, deployment, security, … How will Windows 8.1 fit in your enterprise? How do you upgrade? All answers are here!
This document provides an overview and demonstration of the Microsoft Web Platform tools: IIS Web Eco-System, Web Platform Installer (Web PI), and Web Deploy. The presentation covers the main components and features of each tool, how they work, and examples of common usage scenarios. Web PI simplifies installation of web software. Web Deploy enables deployment and synchronization of websites, applications, and databases between IIS servers. Usage scenarios demonstrated include synchronization, migration, packaging, and modifying sync behavior with rules.
- InstallAware is a software that simplifies the creation of Windows installer packages by abstracting the complexities of Windows Installer technology. It allows developers to build installers using a simple scripting language called MSIcode instead of programming custom actions.
- InstallAware can reduce the size of installer packages by up to 67% using advanced compression techniques. It also makes it easy to deploy runtime dependencies and optional application features on demand.
- In addition to simplifying installer authoring, InstallAware provides features to help developers manage customer relationships, consolidate multiple product editions into a single installer, and perform web-based software updates.
The document outlines the agenda and topics that will be covered in a training on MSI/Windows Installer for NGN. It includes an introduction, overview of legacy installers vs Windows Installer, details on key concepts like packages, products, components, features, properties, and more. It also discusses ICE validation, caching, rights management, and versions. The training will cover tools like AdminStudio and installing/configuring common applications.
Advanced Debugging with Visual Studio 2013 PreviewDanijel Malik
The document outlines the advanced debugging features in Visual Studio 2013 Preview, including what's new for debugging, basics like breakpoints and data tips, debug windows, code interaction with the debugger, multi-threaded and parallel debugging, IntelliTrace, remote debugging, and memory dumps. The key areas covered are editing and continuing for x64, viewing method return values, debugging managed memory, Code Map debugging, tasks for async/await, and using IntelliTrace in Visual Studio or standalone.
This document discusses how to automatically and rapidly deploy software in a small environment. It covers the two main parts of the process: software packaging and software deployment. For packaging, it explains how to configure software installations to run silently without user input using techniques like installation switches, MSI properties, and diff tools. For deployment, it discusses options like GPSI, PSExec, and paid solutions to remotely install packaged software on machines.
The document outlines the steps for performing a standard Oracle E-Business Suite installation and an express installation. A standard installation involves 26 steps to configure the system, database, applications nodes, and perform the installation. An express installation provides a simplified single-user setup with default configurations in 6 steps.
The document discusses preparing software for automated deployment after upgrading to Windows 7. It covers two key aspects: repackaging software to install silently without user input, and deploying the repackaged software using a deployment tool. For repackaging, it describes analyzing the installation format (EXE, MSI, etc.), identifying any silent installation switches, and using tools like WinINSTALL LE to capture changes if switches cannot be found. It also discusses customizing software post-installation using registry changes packaged via these same tools.
This document provides steps to deploy Oracle Hyperion Financial Close Management on a single server running Windows. The 6 hour deployment process involves:
1. Downloading installation files, including Oracle Database and EPM system files.
2. Installing and configuring Oracle Database, creating the 'fcm' and 'DEV_ODI_REPO' database users.
3. Installing and configuring the EPM system, including Oracle SOA Suite, Oracle Data Integrator, and Account Reconciliation Manager.
4. Configuring Oracle Data Integrator and ERPI for Account Reconciliation Manager.
This document provides instructions for installing SwiftConfigurator software. It outlines requirements for the operating system, database, application server, and browser. It describes how to configure the Oracle 11g database and Application Server 10g. Steps are provided for deploying the SwiftConfigurator application and configuring datasources. Additional setup information is also included for language settings and known issues.
The document discusses improvements to Windows Server 2008 management tools, including Server Manager, Event Viewer, and PowerShell. Server Manager provides a unified interface for server configuration and management. Event Viewer allows for improved event logging, organization, and searching. PowerShell introduces a new interactive shell and scripting language that provides over 130 commands and allows for automation of server administration tasks.
The document discusses improvements to Windows Server 2008 management tools, including Server Manager, Event Viewer, and PowerShell. Server Manager provides a unified interface for server configuration and management. Event Viewer allows for improved event logging, organization, and searching. PowerShell introduces a powerful new scripting language and interactive shell based on .NET. It provides over 130 new commands and allows for automation of server administration tasks.
This document summarizes key points about application compatibility between Windows versions. Most software that runs on Windows Vista will also run on Windows 7, with some exceptions for low-level code. Hardware compatible with Vista will also generally work with 7. While there are few surface-level changes, under the hood there are deeper changes to security, drivers, deployment and networking. The document outlines specific compatibility issues applications may face when moving from XP to 7 or Vista to 7, such as new folder locations and changes due to User Account Control. It provides recommendations on using new Windows 7 APIs and features to enhance applications.
This document provides summaries of various free tools for Windows server administration. It is organized into sections covering server and security tools, file and disk tools, and network monitoring and troubleshooting tools. For each tool, a brief description is given along with the download link. Over 50 different tools are mentioned and summarized.
This document provides an overview of Visual Studio .NET 2005, including its various editions, new features, and system requirements. It discusses the Express, Standard, and Professional editions. Key new features include code snippets, refactoring tools, and improved debugging capabilities. The document also announces upcoming .NET events and links to additional information resources.
MS Cloud Day - Deploying and monitoring windows azure applicationsSpiffy
This document discusses how to deploy and monitor applications on Windows Azure. It covers deploying applications through the Azure portal, Visual Studio, and PowerShell cmdlets. It also discusses upgrading applications using in-place upgrades, VIP swaps, and deleting and recreating deployments. The document reviews monitoring applications using the diagnostic API and visualizing collected data. It also demonstrates installing programs and using startup tasks on Azure roles.
Yu Guan provides best practices for developing Windows services including:
- Separating business logic into individual projects for implementation segmentation.
- Using an installer component marked with the [RunInstaller(true)] attribute for installation.
- Debugging services by running in console, attaching a process, or using Debugger.Launch() and Debugger.Break().
- The DevLib.ServiceProcess NuGet package and source code on CodePlex which provides an easy way to port services and solve common pain points.
The document discusses tools and techniques for rapidly deploying software in an environment. It covers two aspects: software packaging and software deployment. For packaging, it explains how to analyze installers and configure them for silent/unattended installation. For deployment, it discusses using tools like Group Policy to distribute packaged software and custom configurations across an environment.
This document provides instructions for running the Studio Database Gateway application as a Windows service on a remote computer. It describes downloading the Windows Resource Kit tools, using the SRVANY and SC commands to create the service, editing the registry to configure the service to launch the gateway application, and configuring Windows Firewall to allow remote access. Configuring the database connection in the InTouch Machine Edition involves specifying the hostname or IP address of the remote computer running the gateway service.
The document discusses various .NET debugging techniques, including:
1. The importance of debugging and the tools available for debugging .NET applications, such as Visual Studio and Debugging Tools for Windows.
2. Basic debugging tasks like setting breakpoints, stepping through code, and examining variables and call stacks.
3. Advanced techniques like debugging managed code, threads, and memory issues.
Similar to Troubleshooting the Windows Installer (20)
2. Bob Kelly
AppDeploy Library
http://www.appdeploy.com/library
Windows Vista community
http://www.realtime-vista.com
Author and editor for several books, articles and
papers on the topics of scripting and desktop
administration…
http://www.bkelly.com
4. Interpreting Errors
The errors reported by Windows Installer
are internal errors
Keep a print out of the errors and their
definitions.
Microsoft Windows SDK (Vista) Documentation
Win32 and COM Development > Administration and
Management > Application Installation and Servicing >
Windows Installer > Windows Installer Reference > Error
Reference > Windows Installer Error Messages
MSDN Library Online
http://msdn2.microsoft.com/en-us/library/aa372835.aspx
AppDeploy Online Reference
http://www.appdeploy.com/msierrors/
5. Controlling Logs
Logging Values (voice warm up)
V = Verbose output
O = Out of disk space messages
I = Status messages
C = Initial UI parameters
E = All error messages
W = Non-fatal warnings
A = Startup of actions
R = Action-specific records
M = Out of memory or fatal exit information
U = User requests
P = Show properties
+ = Append to existing file
! = Empty the logging cache
13. Reading Logs
Use the find function to locate instances of
the keyword “error”
Installer log return codes for logged
actions
0 = Action not invoked; may not exist
1 = Completed actions successfully
2 = User terminated prematurely
3 = Unrecoverable error occurred
4 = Sequence suspended, to resume later
15. Obtaining Tools
Windows SDK for Windows Vista and .NET
Framework 3.0 Runtime Components
Choose: Developer Tools > Windows Development
Tools > Win32 Development Tools
http://download.microsoft.com/download/a/7/7/a7767f09-0136-4a96-
a1f8-276bf0ee31fa/Setup.exe
Windows Installer SDK (v1)
http://www.microsoft.com/downloads/details.aspx?FamilyID=e96f8abc-
62c3-4cc3-93ad-bfc98e3ae4a3&DisplayLang=en
AppDeploy.com
http://www.appdeploy.com/techhomes/windowsinstaller.asp
19. MSIZAP
Eliminates all traces of Windows Installer data from the local machine
T = remove all info for given product code
P = remove In-Progress key
S = remove Rollback Information
A = for any specified removal, change ACLs to Admin Full Control
W = perform removal for all users (default is for current user only)
M = remove managed patch registration info
G = remove orphaned cached Windows Installer data files for all users
L = remove corrupted source list information
! = force a positive response to any verification prompts
* = remove all Windows Installer folders and registry keys; adjust shared DLL
counts; stop Windows Installer service
/nologo = Do not display the logo message. This should be the last option
20. ORCA
More like the WordPad vs. the Notepad of
Windows Installer Editors
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/msi/setup/orca_exe.asp
Can be used to perform MSI validation
Supports working with merge modules
Transform creation
Indicates any changes made by a transform
22. Common Errors
Problems with Windows Installer
MSI packages that require Setup.exe
Understanding Application Log Entries
Inaccessible Network Location
Fatal Error During Installation
Invalid Source Location
Common Custom Action Problems
23. Broken Windows Installer
Error 1719: “The Windows Installer service could not be accessed”
Reregister the Windows Installer service
msiexec /unregister
msiexec /regserver
Reinstallation or upgrade to latest
24. Dealing with InstallScript
InstallShield Script (InstallScript) has many
benefits for developers, but can be
problematic for administrators due to
requirement for setup.exe
Deploy ISSETUP.MSI beforehand
Remove the SETUP.EXE dependency
Remove custom action that performs the
check using a transform file
Specify a public property (ISSETUPDRIVEN)
at the command line
27. Application Log Entries
Significant events are logged to the
Application Event Log
Products and components are often
identified by GUID
Lookup in Registry
Run install from command line:
msiexec /i <GUID>
29. Inaccessible Network Location
Error 1606: “The feature identifier is not registered.”
Network location cannot be accessed
The CostFinalize action verifies all
potential install folders in directory table
Inadvertent entries
Entries that do not start with a drive letter
Roaming profile location on network in
unavailable share
30. Fatal Error During Install
Error 1603: “A fatal error occurred during installation”
Create verbose log to see actual problem
One common cause: InstallShield Script
DCOM security
1: Event 'E3250601' is created
1: GetInstallDriver, Can not find InstallDriver in ROT
table, Return code = 0x800401e3
1: [GUID]
1: ISMsiServerStartup Failure, Failed to create
InstallDriver, Error = 0x8000401a Action ended
ISMsiServerStartup. Return Value 1603
31. Invalid Source Location
Error 1603: “No valid source could be found for product ”
Always know your source
Use DFS share or consistently available
network drive
Beware of self extracting packages!
32. Common CA Problems
Windows Script Host is not available
WScript.CreateObject
WScript.Quit
WScript.Sleep
WScript.Echo
Know your exit codes (any non-zero return
is failure and will result in rollback)
33. Reference Materials
Microsoft
How to use a setup log file to troubleshoot
setup problems in Office
http://support.microsoft.com/kb/826511
AppDeploy
Windows Installer Error Forum
http://www.appdeploy.com/messageboards/tt.asp?forumid=13
Windows Installer Error Reference
http://www.appdeploy.com/msierrors
Windows Installer Tech Home
http://www.appdeploy.com/techhomes/windowsinstaller.asp
The AppDeploy Library contains an extensive document library and hours of video presentations on system and application deployment topics Admin Script Editor is a powerful suite of scripting tools for Windows Administrators
Interpreting errors- what the different error codes mean and where to find out more about them Controlling logs– the different values and what the real difference is between a verbose and non verbose log Enabling Logging- there are a handful of ways to enable logging and we will briefly cover those Reading Logs– understanding the log files and the information presented.
Windows Installer Error 1603 – “A fatal error occurred during installation” = You need a log! Before discussing where and how to turn on logging, it is important to understand what can be logged… * Wildcard is to log all information except for “V”. To get it all, use “*V”
Verbose obviously logs more information. The hexadecimal values you see in parentheses indicate what process is performing the logged action. With the exception of Windows 9x/ME systems that run all actions as one process, Windows Installer runs installations as two distinct processes: client and server. The client process runs the UI in the user context (collects user information and displays the UI). The server process runs as a service and performs the main installation (executes the installation script). Both processes occur on the same computer and are logged to the same file. This code 2262 here (if we referred to our error list) indicates that the stream is not available– in other words, there are no LaunchConditions specified for this particular package. Not really an error, but just informational– without verbose logging, this is not even called to our attention.
When enabling logging from the command line, you start with whatever action you wish to perform (and log) such as install or uninstall. The MSI file in question and then for the logging value it is /l and then (with no space) what you want to log (voicewarmup). This /lv* gets us everything. Then add a space and provide the path and file name for the log file you wish to generate. The path you specify for the log file must exist or you will get a pop-up message that the log file could not be opened.
With many InstallShield setups you may find that they are wrapped within an executable. The good news from the command line is that you can still pass arguments into the embedded MSI with the /v argument. The /v argument must be the last InstallShield parameter on the command line. Though supported Windows Installer parameters may be passed through to the MSI package, no InstallShield command-line parameters can follow the /v argument. Although it was not really necessary in this example, I wanted to show that if you need to put quotes in the command line (such as when dealing with spaces) – because the /v argument itself is enclosed in quotes, you must precede any quotes with a backslash to “escape” them.
Some setups such as MS office, provide an INI file for the setup which you may modify to dictate the behavior of the installation. For office, this file is to be stored at the admin installation point in a subfolder named “setup”. There is even a Setup INI customization wizard to help you manage this file. There is a logging section and you can change the type value to reflect what it is you want logged. You can also specify a path for log files by adding a Path value to this logging section. If you modify the Setup.ini file in the Files\\Setup folder of your administrative installation, you do not need a custom command line. However, if you rename the modified Setup.ini file, or it is located in a location other than the Files\\Setup folder of your Office installation, use a command line that is similar to the following to reference the new settings file More: http://support.microsoft.com/kb/308279
If installing via group policy or if you want to log the installation of an advertised package (or first use feature) you don ’t have these command line options available. For these we can edit the registry or use group policy… The wildcard does not work well here, use VOICEWARMUP to get a good log.
The policy is located under computer configuration > administrative templates > windows components > Windows Installer – here you can set your logging control values we discussed earlier (voicewarmup) When set to run via policy (either by registry edit or policy edit) you do not have the ability to specify the path for the log file– they are generated in the %temp% folder with a randomly generated name that starts with MSI and ends with .LOG. If the setup is running via group policy with nobody logged on, the log file will appear in the windows/temp folder. So if you don ’t see it in your temp folder, check there.
Quite often one error will generate another and so forth. Therefore you may see several errors when you view a log file. It can sometimes be the case that the error returned in the end is not always the cause but may be the result of an earlier error. The error returned is often helpful, but the entries in a verbose log leading up to the error can sometimes be even more revealing. When searching this log– start from the top of the file an search for the word “error”. You may be used to seeing zero to indicate success; not here . A return value of 4 typically means that the action cannot be completed until the computer is restarted.
Now one very helpful tool to analyzing logs is WiLogUtil from Microsoft. This is a good segway into the other freely available tools you may make use of in troubleshooting problems so I ’ll take a quick time out from the log discussion to cover how to obtain these tools…
For administrators InstallScript adds an additional level of complication in the need for installation of the InstallScript Runtime. To ensure that the required InstallScript Runtime is available MSI packages that utilize it must be launched from an accompanying setup.exe which can perform a check and if necessary an installation/upgrade of InstallScript as well as any custom InstallScript code prior to proceeding with the call to the MSI package. This makes it difficult to deploy- particularly via Group Policy which requires an MSI directly. It also makes it difficult to customize as you cannot create a response transform with most tools (all request a target MSI which is launched, in this case an MSI that cannot be launched directly). Further, this can make it difficult to include the installation using any conflict detection/resolution utilities.
Any pop up messages (or would be pop up messages) appear in the Application Log
Any directories in the Directory table will be validated by the CostFinalize sequence. Any entries that do not start with a drive letter are seen as network paths. If you have a mapped drive or redirected folder listed and the package is running with no user logged on, these paths may be inaccessible. Clean up your Directory table.
In particular if you do not handle when a custom action will run, it may try to run during uninstall. If this will fail, then your uninstall will fail and rollback to a “installed” state when you try to remove it. To fix this you would need to edit the locally cached MSI in the Installer directory or use MSIZAP. The installer runs script custom actions directly and does not use the Windows Script Host. The WScript object cannot be used inside a script custom action because this object is provided by the Windows Script Host. Objects in the Windows Script Host object model can only be used in custom actions if Windows Script Host is installed on the computer by creating new instances of the object, with a call to CreateObject, and providing the ProgId of the object (for example "WScript.Shell"). Depending on the type of script custom action, access to some objects and methods of the Windows Script Host object model may be denied for security reasons.