#sharepoint 2013 powershell get all users in site collection | Explore Tumblr posts and blogs

colorload71 · 4 years ago

Text

Download Cryptolocker Virus For Testing

Nov 12, 2013 The Crypto Locker virus is passed around in emails that have innocent enough looking senders, such as UPS or FedEx, but they’re not really from these corporations, of course. Instead, when you open the attachment, your computer becomes infected and the virus locks all your files until you pay a ransom. Jun 30, 2014 thanks. I see so many new samples (like cryotowall 3.0) that I have moved on from the original cryptolocker. As my antivirus protects against all crypto’s using email/web reputation and also detecting the crypto process, then I am no longer looking for policies to prevent. I am using trend micro worry free 9 with sp1 and the latest hotfix for.

Download Cryptolocker Virus For Testing Tool

Cryptolocker Virus Symantec

Download Cryptolocker Virus For Testing Free

What Is Cryptolocker Virus

Download Cryptolocker Virus For Testing Software

Download Cryptolocker Virus For Testing Sites

What is CryptoLocker?

CryptoLocker is by now a well known piece of malware that can be especially damaging for any data-driven organization. Once the code has been executed, it encrypts files on desktops and network shares and “holds them for ransom”, prompting any user that tries to open the file to pay a fee to decrypt them. For this reason, CryptoLocker and its variants have come to be known as “ransomware.”

Malware like CryptoLocker can enter a protected network through many vectors, including email, file sharing sites, and downloads. New variants have successfully eluded anti-virus and firewall technologies, and it’s reasonable to expect that more will continue to emerge that are able to bypass preventative measures. In addition to limiting the scope of what an infected host can corrupt through buttressing access controls, detective and corrective controls are recommended as a next line of defense.

Get the Free Pen Testing Active Directory Environments EBook

“This really opened my eyes to AD security in a way defensive work never did.”

FYI, this article is CryptoLocker specific. If you’re interested in reading about ransomware in general, we’ve written A Complete Guide To Ransomware that is very in-depth.

Update September 2018: Ransomware attacks have decreased significantly since their peak in 2017. CryptoLocker and it’s variants are no longer in wide distribution, and new ransomware has taken over. Ransomware has evolved as more of a targeted attack instead of the previous wide distribution model, and is still a threat to businesses and government entities.

What Does CryptoLocker Do?

On execution, CryptoLocker begins to scan mapped network drives that the host is connected to for folders and documents (see affected file-types), and renames and encrypts those that it has permission to modify, as determined by the credentials of the user who executes the code.

CryptoLocker uses an RSA 2048-bit key to encrypt the files, and renames the files by appending an extension, such as, .encrypted or .cryptolocker or .(7 random characters), depending on the variant. Finally, the malware creates a file in each affected directory linking to a web page with decryption instructions that require the user to make a payment (e.g. via bitcoin). Instruction file names are typically DECRYPT_INSTRUCTION.txt or DECRYPT_INSTRUCTIONS.html.

As new variants are uncovered, information will be added to the Varonis Connect discussion on Ransomware. For example, a variant known as “CTB-Locker” creates a single file in the directory where it first begins to encrypt files, named, !Decrypt-All-Files-(RANDOM 7 chars).TXT or !Decrypt-All-Files-(RANDOM 7 chars).BMP.

How to Prevent CryptoLocker

The more files a user account has access to, the more damage malware can inflict. Restricting access is therefore a prudent course of action, as it will limit the scope of what can be encrypted. In addition to offering a line of defense for malware, it will mitigate potential exposure to other attacks from both internal and external actors.

While getting to a least privilege model is not a quick fix, it’s possible to reduce exposure quickly by removing unnecessary global access groups from access control lists. Groups like “Everyone,” “Authenticated Users,” and “Domain Users,” when used on data containers (like folders and SharePoint sites) can expose entire hierarchies to all users in a company. In addition to being easy targets for theft or misuse, these exposed data sets are very likely to be damaged in a malware attack. On file servers, these folders are known as “open shares,” if both file system and sharing permissions are accessible via a global access group.

Although it’s easiest to use technologies designed to find and eliminate global access groups, it is possible to spot open shares by creating a user with no group memberships, and using that account’s credentials to “scan” the file sharing environment. For example, even basic net commands from a windows cmd shell can be used to enumerate and test shares for accessibility:

net view (enumerates nearby hosts)

net view host (enumerates shares)

net use X: hostshare (maps a drive to the share)

dir /s (enumerates all the files readable by the user under the share)

These commands can be easily combined in a batch script to identify widely accessible folders and files. Remediating these without automation, unfortunately, can be a time-consuming and risky endeavor, as it’s easy to affect normal business activity if you’re not careful. If you uncover a large amount of accessible folders, consider an automated solution. Automated solutions can also help you go farther than eliminating global access, making it possible to achieve a true least-privilege model and eliminate manual, ineffective access-control management at the same time.

How to Detect CryptoLocker

If file access activity is being monitored on affected files servers, these behaviors generate very large numbers of open, modify, and create events at a very rapid pace, and are fairly easy to spot with automation, providing a valuable detective control. For example, if a single user account modifies 100 files within a minute, it’s a good bet something automated is going on. Configure your monitoring solution to trigger an alert when this behavior is observed. Varonis DatAlert monitors and tracks file system behavior for ransomware attacks out-of-the-box. There is no need for extra configuration if Varonis is monitoring your data.

If you don’t have an automated solution to monitor file access activity, you may be forced to enable native auditing. Native auditing, unfortunately, taxes monitored systems and the output is difficult to decipher. Instead of attempting to enable and collect native audit logs on each system, prioritize particularly sensitive areas and consider setting up a file share honeypot.

A file share honeypot is an accessible file share that contains files that look normal or valuable, but in reality are fake. As no legitimate user activity should be associated with a honeypot file share, any activity observed should be scrutinized carefully. If you’re stuck with manual methods, you’ll need to enable native auditing to record access activity, and create a script to alert you when events are written to the security event log (e.g. using dumpel.exe).

If you’re PowerShell inclined, we’ve written a bit on how to combat CryptoLocker with PowerShell.

If your detective control mechanism can trigger an automated response, such as disabling the user account, the attack is effectively stopped before inflicting further damage. For example, a response to a user that generates more than 100 modify events within a minute might include:

Notifying IT and security administrators (include the affected username and machine)

Checking the machine’s registry for known keys/values that CryptoLocker creates:

Get-Item HKCU:SoftwareCryptoLockerFiles).GetValueNames()

if value exists, disable user automatically.

Download Cryptolocker Virus For Testing Tool

If recorded access activity is preserved and adequately searchable, it becomes invaluable in recovery efforts, as it provides a complete record of all affected files, user accounts, and (potentially) hosts. Varonis customers can use the output from report 1a (as described here) to restore files from a backup or shadow copy.

Depending on the variant of CryptoLocker, encryption may be reversible with a real-time disassembler.

Ransomware Safety Tips

Update your antivirus and endpoint protection software – these solutions can help detect certain types of ransomware and prevent it from encrypting your files.

Avoid phishing scams – phishing emails are the most prevalent delivery mechanism for ransomware.

Keep backups of your documents – it’s much faster and easier to recover your documents from a backup than it is to decrypt them, if they’ve been compromised in a ransomware attack.

Commit to a zero-trust/least privilege model – ransomware can only affect the folders a user can write to. A least privilege model limits that access to only what’s absolutely necessary.

Monitor file activity and user behavior to detect, alert and respond to potential ransomware activity.

New ransomware variants are popping up all the time – luckily our dedicated security forensics team does the legwork for you and diligently updates the ransomware signatures that Varonis detects. See how it works with a free 1:1 demo and learn more about how our ransomware defense architecture is designed to protect enterprise data from zero-day attacks beyond the endpoint – catching ransomware that traditional perimeter security doesn’t see.

If you ever needed a reminder to be careful about the emails and attachments you open, it’s now. The Crypto Locker virus that is going around is said to be one of the worst ever and is infecting computers with the Windows OS all across the United States. The virus, also called “ransomware,” works by holding your files hostage until you pay a fee.

The Crypto Locker virus is passed around in emails that have innocent enough looking senders, such as UPS or FedEx, but they’re not really from these corporations, of course. Instead, when you open the attachment, your computer becomes infected and the virus locks all your files until you pay a ransom. Check out a picture of what the Crypto Locker demand screen looks like:

Cryptolocker Virus Symantec

Well i found this sample on my PC i when i was scanning my box. 😛 anyways might be this sample is useful for you.Please handle with care.

RAR Pass: 123

Download Cryptolocker Virus For Testing Free

Download from here !

What Is Cryptolocker Virus

[email protected]

Download Cryptolocker Virus For Testing Software

[email protected]

Download Cryptolocker Virus For Testing Sites

Tushar Verma (c0d3369)

0 notes

galactissolutions · 8 years ago

Text

55095: SharePoint 2010 and 2013 Auditing and Site Content Administration using PowerShell, thailand

55095: SharePoint 2010 and 2013 Auditing and Site Content Administration using PowerShell

55095: SharePoint 2010 And 2013 Auditing And Site Content Administration Using PowerShell Course DescriptionDuration: 5.00 days (40 hours)

This one day class is designed for SharePoint 2010 and 2013 server administrators and auditors who need to query just about anything in SharePoint. The class handout is effectively a cheat sheet with over 175 PowerShell scripts plus the general patterns to create your own scripts. These scripts cover:

using the SharePoint Management Shell and the ISE

general tips for counting, reformatting and exporting results;

understand and drilling up and down the SharePoint object model

getting lists / inventories of servers, services web applications, sites, webs, lists, libraries, items, fields, content types, users and much more

finding lists by template type, content type and types of content finding files by user, content type, file extension, checked out status, size and age

finding inactive sites

finding and changing SharePoint Designer settings and finding and resetting customized pages

inventorying and managing features

deleting and recycling files and list items

inventorying users and user permissions and finding out who can access what

creating sites, lists and libraries

uploading and downloading files

and much more

Intended Audience For This 55095: SharePoint 2010 And 2013 Auditing And Site Content Administration Using PowerShell Course

» SharePoint server administrators.

» SharePoint auditors.

» Also valuable for SharePoint developers.

55095: SharePoint 2010 And 2013 Auditing And Site Content Administration Using PowerShell Course Objectives

» Use PowerShell to query just about anything inside of SharePoint.

» Understand the core SharePoint object model and object hierarchy as seen from PowerShell.

» Format PowerShell output in to reports.

» Manage resources to limit the impact on production servers.

» Create and delete Site Collections, subsites, lists, libraries and content.

55095: SharePoint 2010 And 2013 Auditing And Site Content Administration Using PowerShell Course Outline

History of PowerShell in SharePoint

PowerShell vs. Search

PowerShell, SharePoint Management Shell and cmdlets

Security and Permissions Needed

Getting Started with PowerShell: Counting Items, Custom Columns, Reformatting Numbers, Saving Results to a File

Changing and Updating Content: Creating SharePoint Objects, Changing Objects

Lab : Using PowerShell with SharePoint

Using PowerShell with SharePoint

GUIDs

Sites vs. Webs

The SharePoint Object Hierarchy

Lab : Working with SharePoint CMDLETs and Objects

Get a list of all Site Collections and their GUIDs

Get a list of all Webs in all Site Collections

Given a webs URL get its parent web and web application

Memory Management and Disposing Objects

Limiting Impact on Production Servers

Lab : Managing Memory and Limiting Performance Impact

Exploring PowerShells use of system memory.

Testing the impact of scripts on server performance

Getting Farm Information: version, services, services, features

Getting Web Application information

Exploring Site Collections: retrieve Site Collections, Site Collection Administrators, quotas

Working with the Recycle Bins: finding items, getting file counts and bytes, deleted sites

Exploring Webs: web templates, finding webs, finding webs based on template, Quick Launch and Top Link Bar navigation

Exploring Lists and Libraries: finding all lists, lists by type, lists by Content Type, columns/fields, document count by web or library

Exploring Content Types

Finding documents: by a word in the title, file type, content type, size, date age, checked out status, approval status and many more�?�

Deleting content

Downloading and uploading files

Lab : Working with Content

Explore the farm.

Inventory site collections.

Create a recycle bin report.

Finding all blog sites.

Find all picture libraries.

Find all PDF files over 5 MB.

Delete all videos in a site collection.

Users: find a user, get a list of all users, working with Active Directory groups

SharePoint groups: Get lists of groups, get the members of a group, find all groups a user belongs to, find the groups associated with a web

Expanding users lists that include Active Directory groups

Documenting Broken Inheritance / Unique Permissions: webs, lists, libraries, folders, items

Working with Role Assignments

Lab : Users and Security

Get a list of all users who have access to a Site Collection.

Get a list of all groups in a Site Collection.

Get a list of all groups a user belongs to.

List all users who may have access to a SharePoint securable.

Get a list of all securables with broken inheritance.

Finding Inactive Webs

Creating and Deleting Site Collections

Getting Site Collection Data

Creating and Deleting Subsites

Working With SharePoint Designer Settings

Lab : Managing Sites

Create a report for inactive sites.

Create a site collection and subsites.

Delete a site.

Delete a site collection.

Disable SharePoint Designer in all site collections.

0 notes

stormdoors78476 · 8 years ago

Text

DSC Resource Kit Release May 2017

We just released the DSC Resource Kit!This release includes updates to 10 DSC resource modules including 3 new resources. In these past 6 weeks, 60 pull requests have been merged and 58 issues have been closed, all thanks to our amazing community!

The modules updated in this release are:

SharePointDsc

SecurityPolicyDsc

xCertificate

xComputerManagement

xCredSSP

xExchange

xHyper-V

xNetworking

xSqlServer

xStorage

PSDscResources and xDFS are also in the pipeline for release, but they are currently failing tests. They will be released when tests are passing.

For a detailed list of the resource modules and fixes in this release, see the Included in this Release section below.

Our last community call for the DSC Resource Kit was last week on May 24. A recording of our updates as well as summarizing notes are available. Join us next time to ask questions and give feedback about your experience with the DSC Resource Kit. Keep an eye on the community agenda for the link to the next call.

We strongly encourage you to update to the newest version of all modules using the PowerShell Gallery, and don’t forget to give us your feedback in the comments below, on GitHub, or on Twitter (@PowerShell_Team)!

All resources with the ‘x’ prefix in their names are still experimental – this means that those resources are provided AS IS and are not supported through any Microsoft support program or service. If you find a problem with a resource, please file an issue on GitHub.

Included in this Release

You can see a detailed summary of all changes included in this release in the table below. For past release notes, go to the README.md or Changelog.md file on the GitHub repository page for a specific module (see the How to Find DSC Resource Modules on GitHub section below for details on finding the GitHub page for a specific module).

Module Name Version Release Notes SharePointDsc 1.7.0.0

Update SPSearchIndexPartition made ServiceAppName as a Key

New resouce: SPTrustedRootAuthority

Update SPFarmSolution to eject from loop after 30m.

New resource: SPMachineTranslationServiceApp

New resource: SPPowerPointAutomationServiceApp

Bugfix in SPSearchFileType made ServiceAppName a key property.

New resource: SPWebApplicationExtension

Added new resource SPAccessServices2010

Added MSFT_SPSearchCrawlMapping Resource to manage Crawl Mappings for Search Service Application

Added new resource SPSearchAuthoritativePage

Bugfix in SPWebAppThrottlingSettings for setting large list window time.

Fix typo in method Get-TargetResource of SPFeature

Fix bug in SPManagedAccount not returning the correct account name value

Fix typo in method Get-TargetResource of SPSearchIndexPartition

Update documentation of SPInstallLanguagePack to add guidance on package change in SP2016

Added returning the required RunCentralAdmin parameter to Get-TargetResource in SPFarm

Added web role check for SPBlobCacheSettings

Improved error message when rule could not be found in SPHealthAnalyzerRuleState

Extended the documentation to specify that the default value of Ensure is Present

Added documentation about the user of Host Header Site Collections and the HostHeader parameter in SPWebApplication

Fixed missing brackets in SPWebAppPolicy module file

Fixed issue with SPSecureStoreServiceApp not returning database information

Fixed issue with SPManagedMetadataServiceApp not returning ContentTypeHubUrl in SP2016

Updated SPTrustedIdentityTokenIssuer to allow to specify the signing certificate from file path as an alternative to the certificate store

New resource: SPSearchCrawlerImpactRule

Fixed issue in SPSite where the used template wasn’t returned properly

Fixed issue in SPWebApplicationGeneralSettings which didn’t return the security validation timeout properly

Fixed bug in SPCreateFarm and SPJoinFarm when a SharePoint Server is already joined to a farm

Bugfix in SPContentDatabase for setting WarningSiteCount as 0.

Fixing verbose message that identifies SP2016 as 2013 in MSFT_SPFarm

Fixed SPProductUpdate looking for OSearch15 in SP2016 when stopping services

Added TermStoreAdministrators property to SPManagedMetadataServiceApp

Fixed an issue in SPSearchTopology that would leave a corrupt topology in place if a server was removed and re-added to a farm

Fixed bug in SPFarm that caused issues with database names that have dashes in the names

SecurityPolicyDsc 1.4.0.0

Added functionality to support BaselineManagement Module.

Updated UserRightsAssignment resource to respect dynamic local accounts.

Added SecuritySetting resource to process additional INF settings.

xCertificate 2.6.0.0

Added mandatory properties for xPfxImport resource example.

xCertReq:

Fixed issue where xCertReq does not identify when DNS Names in SANs are incorrect.

Added Certificate Authority auto-discovery to resource xCertReq.

Added SAN and certificate template name to xCertReq”s Get-TargetResource

Added new parameter UseMachineContext to be able to use CA templates that try to fill the subject alternative name

CertificateDSc.Common:

Added function Get-CertificateTemplateName to retrieve template name

Added function Get-CertificateSan to retrieve subject alternative name

Added function Find-CertificateAuthority to enable auto-discovery

xComputerManagement 1.10.0.0

Added resources

xVirtualMemory

xCredSSP 1.3.0.0

Added a fix to enable credSSP with a fresh server installation

xExchange 1.15.0.0

xExchDatabaseAvailabilityGroupMember: Added check to ensure Failover-Clustering role is installed before adding server to DAG.

xExchInstall: Remove parameter “-AllowImmediateReboot $AllowImmediateReboot” when calling CheckWSManConfig.

xExchOutlookAnywhere: Add test for ExternalClientAuthenticationMethod.

Test: Update OAB and UMService tests to create test OAB and UMDialPlans, respectively.

xHyper-V 3.8.0.0

Fix bug in xVMDvdDrive with hardcoded VM Name.

Corrected Markdown rule violations in Readme.md.

xNetworking 4.0.0.0

Converted to use AppVeyor.psm1 in DSCResource.Tests repository.

Converted to use Example and Markdown tests in DSCResource.Tests repository.

Added CodeCov.io support.

Added a new example to xDNSServerAddress to clarify setting multiple DNS Servers.

Fix examples to correct display in auto documentation generation.

BREAKING CHANGE: Migrated xNetworkAdapter module functionality to xNetAdapterName resource.

Added CommonTestHelper module for aiding testing.

MSFT_xNetAdapterName:

Created new resource for renaming network adapters.

Added Find-NetAdapter cmdlet to NetworkingDsc.Common.

Correct example parameters format to meet style guidelines.

xSqlServer 7.1.0.0

Changes to xSQLServerMemory

Changed the way SQLServer parameter is passed from Test-TargetResource to Get-TargetResource so that the default value isn”t lost (issue 576).

Added condition to unit tests for when no SQLServer parameter is set.

Changes to xSQLServerMaxDop

Changed the way SQLServer parameter is passed from Test-TargetResource to Get-TargetResource so that the default value isn”t lost (issue 576).

Added condition to unit tests for when no SQLServer parameter is set.

Changes to xWaitForAvailabilityGroup

Updated README.md with a description for the resources and revised the parameter descriptions.

The default value for RetryIntervalSec is now 20 seconds and the default value for RetryCount is now 30 times (issue 505).

Cleaned up code and fixed PSSA rules warnings (issue 268).

Added unit tests (issue 297).

Added descriptive text to README.md that the account that runs the resource must have permission to run the cmdlet Get-ClusterGroup (issue 307).

Added read-only parameter GroupExist which will return $true if the cluster role/group exist, otherwise it returns $false (issue 510).

Added examples.

Changes to xSQLServerPermission

Cleaned up code, removed SupportsShouldProcess and fixed PSSA rules warnings (issue 241 and issue 262).

It is now possible to add permissions to two or more logins on the same instance (issue 526).

The parameter NodeName is no longer mandatory and has now the default value of $env:COMPUTERNAME.

The parameter Ensure now has a default value of “Present”.

Updated README.md with a description for the resources and revised the parameter descriptions.

Removed dependency of SQLPS provider (issue 482).

Added ConnectSql permission. Now that permission can also be granted or revoked.

Updated note in resource description to also mention ConnectSql permission.

Changes to xSQLServerHelper module

Removed helper function Get-SQLPSInstance and Get-SQLPSInstanceName because there is no resource using it any longer.

Added four new helper functions.

Register-SqlSmo, Register-SqlWmiManagement and Unregister-SqlAssemblies to handle the creation on the application domain and loading and unloading of the SMO and SqlWmiManagement assemblies.

Get-SqlInstanceMajorVersion to get the major SQL version for a specific instance.

Fixed typos in comment-based help

Changes to xSQLServer

Fixed typos in markdown files; CHANGELOG, CONTRIBUTING, README and ISSUE_TEMPLATE.

Fixed typos in schema.mof files (and README.md).

Updated some parameter description in schema.mof files on those that was found was not equal to README.md.

Changes to xSQLServerAlwaysOnService

Get-TargetResource should no longer fail silently with error “Index operation failed; the array index evaluated to null.” (issue 519). Now if the Server.IsHadrEnabled property return neither $true or $false the Get-TargetResource function will throw an error.

Changes to xSQLServerSetUp

Updated xSQLServerSetup Module Get-Resource method to fix (issue 516 and 490).

Added change to detect DQ, DQC, BOL, SDK features. Now the function Test-TargetResource returns true after calling set for DQ, DQC, BOL, SDK features (issue 516 and 490).

Changes to xSQLServerAlwaysOnAvailabilityGroup

Updated to return the exception raised when an error is thrown.

Changes to xSQLServerAlwaysOnAvailabilityGroupReplica

Updated to return the exception raised when an error is thrown.

Updated parameter description for parameter Name, so that it says it must be in the format SQLServer\InstanceName for named instance (issue 548).

Changes to xSQLServerLogin

Added an optional boolean parameter Disabled. It can be used to enable/disable existing logins or create disabled logins (new logins are created as enabled by default).

Changes to xSQLServerDatabaseRole

Updated variable passed to Microsoft.SqlServer.Management.Smo.User constructor to fix issue 530

Changes to xSQLServerNetwork

Added optional parameter SQLServer with default value of $env:COMPUTERNAME (issue 528).

Added optional parameter RestartTimeout with default value of 120 seconds.

Now the resource supports restarting a sql server in a cluster (issue 527 and issue 455).

Now the resource allows to set the parameter TcpDynamicPorts to a blank value (partly fixes issue 534). Setting a blank value for parameter TcpDynamicPorts together with a value for parameter TcpPort means that static port will be used.

Now the resource will not call Alter() in the Set-TargetResource when there is no change necessary (issue 537).

Updated example 1-EnableTcpIpOnCustomStaticPort.

Added unit tests (issue 294).

Refactored some of the code, cleaned up the rest and fixed PSSA rules warnings (issue 261).

If parameter TcpDynamicPort is set to “0” at the same time as TcpPort is set the resource will now throw an error (issue 535).

Added examples (issue 536).

When TcpDynamicPorts is set to “0” the Test-TargetResource function will no longer fail each time (issue 564).

Changes to xSQLServerRSConfig

Replaced sqlcmd.exe usages with Invoke-Sqlcmd calls (issue 567).

Changes to xSQLServerDatabasePermission

Fixed code style, updated README.md and removed *-SqlDatabasePermission functions from xSQLServerHelper.psm1.

Added the option “GrantWithGrant” with gives the user grant rights, together with the ability to grant others the same right.

Now the resource can revoke permission correctly (issue 454). When revoking “GrantWithGrant”, both the grantee and all the other users the grantee has granted the same permission to, will also get their permission revoked.

Updated tests to cover Revoke().

Changes to xSQLServerHelper

The missing helper function (“Test-SPDSCObjectHasProperty”), that was referenced in the helper function Test-SQLDscParameterState, is now incorporated into Test-SQLDscParameterState (issue 589).

xStorage 3.0.0.0

Converted AppVeyor build process to use AppVeyor.psm1.

Added support for auto generating wiki, help files, markdown linting and checking examples.

Correct name of MSFT_xDiskAccessPath.tests.ps1.

Move shared modules into Modules folder.

Fixed unit tests.

Removed support for WMI cmdlets.

Opted in to Markdown and Example tests.

Added CodeCov.io support.

Removed requirement on using Pester 3.4.6 because Pester bug fixed in 4.0.3.

Fixed unit tests for MSFT_xDiskAccessPath resource to be compatible with Pester 4.0.3.

xDisk:

BREAKING CHANGE: Renamed parameter DiskNumber to DiskId to enable it to

See Issue 81.

Added DiskIdType parameter to enable specifying the type of identifer

See Issue 81.

Changed to use xDiskAccessPath pattern to fix issue with Windows Server

See Issue 80.

Fixed style violations in xDisk.

Fixed issue when creating multiple partitions on a single disk with no size

See Issue 86.

xDiskAccessPath:

BREAKING CHANGE: Renamed parameter DiskNumber to DiskId to

See Issue 81.

Added DiskIdType parameter to enable specifying the type

See Issue 81.

Fixed incorrect logging messages when changing volume label.

Fixed issue when creating multiple partitions on a single disk with no size

See Issue 86.

xWaitForDisk:

BREAKING CHANGE: Renamed parameter DiskNumber to DiskId

See Issue 81.

Added DiskIdType parameter to enable specifying the type

See Issue 81.

How to Find Released DSC Resource Modules

To see a list of all released DSC Resource Kit modules, go to the PowerShell Gallery and display all modules tagged as DSCResourceKit. You can also enter a module’s name in the search box in the upper right corner of the PowerShell Gallery to find a specific module.

Of course, you can also always use PowerShellGet (available in WMF 5.0) to find modules with DSC Resources:

# To list all modules that are part of the DSC Resource Kit Find-Module -Tag DSCResourceKit # To list all DSC resources from all sources Find-DscResource

To find a specific module, go directly to its URL on the PowerShell Gallery: http://ift.tt/1FzKWKv< module name > For example: http://ift.tt/1IxiVp1

How to Install DSC Resource Modules From the PowerShell Gallery

We recommend that you use PowerShellGet to install DSC resource modules:

Install-Module -Name < module name >

For example:

Install-Module -Name xWebAdministration

To update all previously installed modules at once, open an elevated PowerShell prompt and use this command:

Update-Module

After installing modules, you can discover all DSC resources available to your local system with this command:

Get-DscResource

How to Find DSC Resource Modules on GitHub

All resource modules in the DSC Resource Kit are available open-source on GitHub. You can see the most recent state of a resource module by visiting its GitHub page at: http://ift.tt/1TMedwe< module name > For example, for the xCertificate module, go to: http://ift.tt/1IxiXgI.

All DSC modules are also listed as submodules of the DscResources repository in the xDscResources folder.

How to Contribute

You are more than welcome to contribute to the development of the DSC Resource Kit! There are several different ways you can help. You can create new DSC resources or modules, add test automation, improve documentation, fix existing issues, or open new ones. See our contributing guide for more info on how to become a DSC Resource Kit contributor.

If you would like to help, please take a look at the list of open issues for the DscResources repository. You can also check issues for specific resource modules by going to: http://ift.tt/1TMedwe< module name >/issues For example: http://ift.tt/1JhnNnX

Your help in developing the DSC Resource Kit is invaluable to us!

Questions, comments?

If you’re looking into using PowerShell DSC, have questions or issues with a current resource, or would like a new resource, let us know in the comments below, on Twitter (@PowerShell_Team), or by creating an issue on GitHub.

Katie Keim Software Engineer PowerShell Team @katiedsc (Twitter) @kwirkykat (GitHub)

from DIYS http://ift.tt/2qI5UHn

#DIYS

0 notes

pat78701 · 8 years ago