#i mean no one was questioning it but thank you devs for verifying??? | Explore Tumblr Posts and Blogs

damn-it-a-hogwarts-legacy-blog · 3 months

Text

I can’t believe it’s been a year since I got this game and nine months since I started this blog. Unfortunately, the timing of me getting sick twice in a row these past couple of weeks means I wasn’t able to finish a fic in time to celebrate, but I’m determined to get one out soon! 💚 but I can’t let today pass me by without at least waxing poetic about this game, the community and their impact on me :)

cw: workplace abuse, childhood emotional abuse

This time last year, I was in a very abusive work environment. I was pushed well beyond my limits by people who didn’t care about me or the concerns I raised to them. I was told to shut up, that others had the same workload even though I clearly had more on my one-person “team.” I was a scapegoat. I began having weekly performance reviews in which typos in emails were put in the spotlight and heavily questioned/scrutinized. In the end, they fired me, HR refused to return calls from potential employers to verify employment, and they barred the few coworkers I actually liked from giving me recommendations (I only know because I aggressively pressed one of them after she rescinded an offer to help me), effectively making it twice as difficult to get any new job. I’m in therapy to recover from this experience, but I still carry a large amount of bitterness towards both my former job and myself, and I don’t know if it will ever fully leave me.

I am grouchy and short-tempered. I don’t consider myself to be a nice person or a good friend. My previous work experience solidified what an entire childhood of emotional abuse stemming from my neurodivergence taught me: it’s better to have no trust and be prepared to get angry if people think they can step on me; cut others off at the smallest sign of danger and keep myself at arm’s length from everyone unless absolutely necessary; calculate weakness in my bullies’ tactics and exploit it.

When I first got Hogwarts legacy, I would play maybe a couple hours every week. But what started out as an escape has become a source of healing. I see so much of myself in some of the characters, and seeing some of my pain, mistakes and flaws mirrored in them has given me the ability to give myself a little grace. I see so much of myself in Ominis, and my rabid need to write him receiving the love and healing I want/need has been extremely therapeutic.

Joining the HLDS dev team was the best thing I ever could have done. I’m finally starting to feel like I can trust some people a little more. The other discord server I’m a part of has been such a positive experience for me too, and I really do love and appreciate everyone there for being so nice to a grouch like me, even if I’m not really sure how to express that most of the time lol. The moots I’m regularly messaging/reblogging/responding to are so important to me. I am so happy you enjoy talking to me, because I adore talking to you too and seeing your notifs gives me such a huge serotonin boost.

Thank you to everyone who makes room for me in discord servers and reads my tumblr posts and talks to me about this game that’s had such a huge impact on me. It really does mean so much more than I could ever express. 💚

#hogwarts legacy #huge middle finger to my former employers obvs #I am now thriving in a way better job in spite of their bullshit and I will continue to spite them for the rest of my natural life #ODD has never been a diagnosis for me but I really do enjoy spiting others with positivity #that goes for both my former employers and anybody tempted to punch down re: my neurodivergence :)

16 notes · View notes

askagamedev · 3 years

Note

Hey, although I have worked on a few solo projects before, I am now starting a team project with a couple of friends on Unity. Unfortunately, we don't really know how to approach the collaboration aspect of game development. I was hoping you could shine some light on how a development team should be working together and properly managing/updating a game throughout the whole game development process. Is there a standard to how we should be doing things to keep the process organized. Thank you!

What you really need for organization is a way to keep all of the project files in order so that you don’t accidentally break the project by accident, and then you need a way to keep all of the future work you need to do so you don’t accidentally waste time or forget to do something important.

The first thing you really need is a revision control system. It’s a piece of software that manages and stores different versions of relevant files in the project. This way you have backups of each file that you can revert back to if something breaks. It also means that the team members can look at the differences between files to see what changes were made by whom over time, in case the project was working yesterday and became broken today. Keeping everything stable and everyone working from a common set of file versions is imperative for managing a project. One of the more common and inexpensive options is Github - it allows people to share code and assets over the internet. They even have a Unity plugin and setup for Unity projects.

The second thing you need is a task management system. This is a way of visibly splitting work up into discrete tasks and subtasks, tracking task progress, prioritizing tasks, and letting your team see who is responsible for which task. For example, if you wanted to add a Level Up system to your game, you’d need to break it into different parts. There’s the UI elements to display relevant information when you level up, a system that manages how much XP each character has, the formula that determines how much experience is needed to level, the defined rewards you get at each level up, and so on. Not all of these tasks need to be completed by the same person; if you have multiple developers, it is very possible to divvy the tasks up between them so that they can work concurrently. Creating, tracking, marking, and verifying tasks is an important organizational aspect of any project - so much so that we have an entire career path in the industry dedicated to doing it for teams. We usually call them producers. Many studios use software solutions like JIRA for handling this sort of work, but you can also use a spreadsheet or even a text document.

Since we can’t read each others’ minds, much of project management is making communication between team members easier and assisting team members with remembering what they need to know. Most teams need this help for their files and for their tasks. These kind of tasks require a significant amount of time spent to keep on top of them but it is far better to spend the time planning than fixing a broken project, dealing with wasted work, or realizing that the work that has been done can’t be used.

[Join us on Discord] and/or [Support us on Patreon]

The FANTa Project is being rebooted. [What is the FANTa project?]

Got a burning question you want answered?

Short questions: Ask a Game Dev on Twitter

Long questions: Ask a Game Dev on Tumblr

Frequent Questions: The FAQ

#project management #working with a team #resource allocation #amateur game design #assembling a team

25 notes · View notes

techyblogger · 2 years

Photo

Directly target your competitors' customers & boost your conversions (Tuwio Launch) https://www.reddit.com/r/SEO/comments/qnpogz/directly_target_your_competitors_customers_boost/

Hey everyone,

I've worked as a web dev, operated ecommerce side hustle, but recently I've been hired by a forward-thinking company which I've helped with growth dev stuff. Together we worked on coming up with creative ideas on cutting customer acquisition costs by 10x (that was the goal) and tried a bunch of things. Really liked working with them, and through the project we came up with a couple of ways, one of them being very striking:

Basically, it's about targeting your competitor's customers directly. We're basically scraping and leveraging a exorbitant amount of publicly available data - the trick is, we're able to match it with a specific company or niche's audience and customers. Then, we go on to vet & verify the lists, making sure they are all real people with engagement to the said brand(s). That means, if we decide to pick 10 companies and create a custom audience list based on their audience and customers, we're able to do that. Works no matter what sector you're targeting, or location, or anything else. Pretty amazing! So, with my co-founder and I, we've decided to turn this into a B2B product for every company to use & boost their ad campaigns - Facebook, Instagram, Google, LinkedIn, even TikTok!

So, for the past few months, we've experimented a lot with the algorithm and ran 3 consecutive paid Beta tests (thank you early believers!), in which there were many redditors I met here! Thank all of you. After concluding the Beta with 93 companies/people/agencies in total, we're very confident in the product ready to launch! It's called Tuwio - we bought the 5-letter domain after some work (that story is for another time, but I'll share if anyone's interested).

In essence, Tuwio means means lower ad costs, higher targetings and conversions! A few examples: One US startup we worked with achieved 7x the amount of conversions they usually get. Another hardware tech company cut their cost per results by ~80%. Another company that does B2B cloud hosting sales was able to target their competitor's audience and now converting them to their company, they were small but their offer was better, but had tough luck with ad-based conversions until Tuwio. Another one was an Etsy shop owner that decided to go direct-to-consumer and now struggling with ecom sales, and now their cost-per-purchase is almost the same as their old cost-per-click, after Tuwio. Now we're in the process of writing these examples as a case study for everyone to see & be inspired. With good creatives, good product & good experience on top of this, one can build a rocketship, basically. The only key thing is to experiment with Tuwio lists a little, and make sure not only the campaign starts well, but scales well - which our support team is excited to help with!

Sorry for the long wall of a post, but we're so excited, and Tuwio is now launched!

You can contact me here by sending a PM, or just send us an email at [email protected] for any questions, requests or to start your journey with us.

Best to you all!

submitted by /u/CardioPumps [link] [comments] November 06, 2021 at 06:56AM

0 notes

cleverninja171 · 3 years

Text

Microsoft Intune Mac Os X Download

Intune and Drive Encryption for Mac OS X Microsoft Intune Thank you for your prompt responses. Naturally I have a few more questions: I presume when you say there is no MAC OS X Intune client you mean that I can. Sep 17, 2018 I have enrolled the Mac OS X laptop to Intune through the Company Portal. The two devices profiles installed are 1. Management Profile and 2. Passcode Profile. The Management Profile's status is verified while the Passcode Profile's status is unverified. As a consequence, none of the password policies are being applied/enforced on the device. Keeping your device up-to-date lets you access the newest features, and it also ensures that your device has the most secure version of its operating system. Microsoft and most major vendors generally recommend keeping both personal and corporate devices on.

Intune Mac Os Management

Intune For Macs

-->

Before you can deploy, configure, monitor, or protect apps, you must add them to Intune. One of the available app types is Microsoft Edge version 77 and later. By selecting this app type in Intune, you can assign and install Microsoft Edge version 77 and later to devices you manage that run macOS. This app type makes it easy for you to assign Microsoft Edge to macOS devices without requiring you to use the macOS app wrapping tool. To help keep the apps more secure and up to date, the app comes with Microsoft AutoUpdate (MAU).

Important

This app type offers developer and beta channels for macOS. The deployment is in English (EN) only, however end users can change the display language in the browser under Settings > Languages.

Note

Microsoft Edge version 77 and later is available for Windows 10 as well.

Prerequisites

The macOS device must be running macOS 10.12 or later before installing Microsoft Edge.

Add Microsoft Edge to Intune

You can add Microsoft Edge version 77 and later to Intune using the following steps:

Office 2016 for Mac Outlook for Mac 2011If you are trying to set up an in Outlook, ask the organization that gave you the email address for the name of your Exchange server. Microsoft server for mac.

Select Apps > All apps > Add.

In the App type list under the Microsoft Edge, version 77 and later, select macOS.

Configure app information

In this step, you provide information about this app deployment. This information helps you identify the app in Intune, and it helps users find the app in the company portal.

Any of those versions brings to access to a wide array of text editing, formatting, collaboration and publishing tools suitable for the needs of every user. With hundreds of millions of daily users, the MS Word Free relies on easy sharing and unified document structure, which includes document types such as.doc,.docx and.dotx.Installation and UseMicrosoft Word is an extensive application that requires a comprehensive installation package, which will extract the app on your PC and integrate it deeply with the functionality of your OS (especially if you are using Windows 10). Its capabilities are suitable for everything from creating and formatting basic text documents, to organizing business documents and managing enterprise workflow. The user interface of the latest MS Word does not step out of tradition, providing large canvas for word editing and a tabbed interface on the top that hold the majority of the app’s tools separated in ten main sections – File (handling of opening and saving of files, exporting, sharing and printing), Home (basic text formatting tools), Insert (home of chart, picture, table, text box, and comment tools), Design, Layout, References, Mailings, Review, View and Help. Download latest microsoft office for mac.

Click App information to display the App information pane.

In the App information pane, you provide information about this app deployment. This information helps you identify the app in Intune, and it helps users find the app in the company portal.

Name: Enter the name of the app as it will be displayed in the company portal. Make sure that all names are unique. If the same app name exists twice, only one of the apps is displayed to users in the company portal.

Description: Enter a description for the app. For example, you could list the targeted users in the description.

Publisher: Microsoft appears as the publisher.

Category: Optionally, select one or more of the built-in app categories or a category that you created. This setting makes it easier for users to find the app when they browse the company portal.

Display this as a featured app in the Company Portal: Select this option to display the app prominently on the main page of the company portal when users browse for apps.

Information URL: Optionally, enter the URL of a website that contains information about this app. The URL is displayed to users in the company portal.

Privacy URL: Optionally, enter the URL of a website that contains privacy information for this app. The URL is displayed to users in the company portal.

Developer: Microsoft appears as the developer.

Owner: Microsoft appears as the owner.

Notes: Optionally, enter any notes that you want to associate with this app.

Select OK.

Configure Microsoft Edge settings

In this step, configure installation options for the app.

Microsoft Office for Mac 2011 gives you a familiar work environment that is more intuitive than ever. The suite provides new and improved tools that make it easy to create professional content, along with improvements in the speed and agility of Office 2011 you will. Download Microsoft Office for Mac 2011 14.6.8 Update from Official Microsoft Download Center. This is your 365. Operating System Versions: Mac OS X version 10.5.8 or a later version of Mac OS. Microsoft office for macbook free.

In the Add App pane, select App settings.

In the App settings pane, select either Stable, Beta or Dev from the Channel list to determine which Edge Channel you will deploy the app from.

Stable channel is the recommended channel for deploying broadly in Enterprise environments. It updates every six weeks, each release incorporating improvements from the Beta channel.

Beta channel is the most stable Microsoft Edge preview experience and the best choice for a full pilot within your organization. With major updates every six weeks, each release incorporates the learnings and improvements from the Dev channel.

Dev channel is ready for enterprise feedback on Windows, Windows Server and macOS. It updates every week and contains the latest improvements and fixes.

Cost of microsoft office 365 for mac. Note https://cleverninja171.tumblr.com/post/656679194170900480/microsoft-outlook-1533-mac.

The Microsoft Edge browser logo is displayed with the app when users browse the company portal.

Select OK.

Select scope tags (optional)

You can use scope tags to determine who can see client app information in Intune. For full details about scope tags, see Use role-based access control and scope tags for distributed IT.

Select Scope (Tags) > Add.

Use the Select box to search for scope tags.

Select the check box next to the scope tags you want to assign to this app.

Click Select > OK.

Add the app

When you've completed configuring, select Add from the App app pane.

Intune Mac Os Management

The app you've created is displayed in the apps list, where you can assign it to the groups that you select.

Note

Currently, Apple does not provide a way for Intune to uninstall Microsoft Edge on macOS devices.

Next steps

Intune For Macs

To learn how to configure Microsoft Edge on macOS devices, see Configure Microsoft Edge on macOS devices.

To learn about including and excluding app assignments from groups of users, see Include and exclude app assignments.

0 notes

repwincoml4a0a5 · 7 years

Text

DSC Resource Kit Release January 2017

We just released the DSC Resource Kit!

This release includes updates to 7 DSC resource modules, including 10 new DSC resources. In these past 6 weeks, 71 pull requests have been merged and 37 issues have been closed, all thanks to our amazing community!

The modules updated in this release are:

AuditPolicyDsc

xDismFeature

xExchange

xNetworking

xPSDesiredStateConfiguration

xSQLServer

xWebAdministration

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

xHyper-V has changes to be released, but the tests have a few issues at the moment. We will release it as soon as those issues are resolved. PSDscResources does not currently have any changes to release, but there are some changes queuing up. We will release it again soon once those changes are ready. We will update this blog post when either of these modules is released.

A new version of xActiveDirectory was also released about two weeks ago with some bug fixes for xADDomain and xADDomainController.

Our last community call for the DSC Resource Kit was last week on January 18. A recording of our updates as well as summarizing notes are available. Join us next time at 9AM PST on March 1 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 call agenda.

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 AuditPolicyDsc 1.1.0.0

Added the AuditPolicyCsv resource.

xDismFeature 1.2.0.0

xDismFeature: Resource no longer includes the Source parameter when it is not specified

Converted appveyor.yml to install Pester from PSGallery instead of from Chocolatey.

xExchange 1.13.0.0

Fix function RemoveVersionSpecificParameters

xExchMailboxServer: Added missing parameters except these, which are marked as “This parameter is reserved for internal Microsoft use.”

xNetworking 3.2.0.0

Fixed typo in the example”s Action property from “Blocked” (which isn”t a valid

value) to “Block”

Added support for auto generating wiki, help files, markdown linting

and checking examples.

Added NetworkingDsc.ResourceHelper module based on copy from PSDscResources.

MSFT_xFirewall:

Cleaned up ParameterList table layout and moved into a new file

(MSFT_xFirewall.data.psd1).

Separated Localization strings into strings file.

Added standard help blocks to all functions to meet HQRM standards.

Added CmdletBinding attribute to all functions to meet HQRM standards.

Style changes to meet HQRM standards.

Fixed issue using CIDR notation for LocalAddress or RemoteAddress.

See GitHub issue.

Fixed integration tests so that values being set are correctly tested.

Added integration tests for Removal of Firewall rule.

Added NetworkingDsc.Common module to contain shared networking functions.

MSFT_xDNSServerAddress:

Separated Localization strings into strings file.

MSFT_xDefaultGatewayAddress:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xDhcpClient:

Separated Localization strings into strings file.

Fix parameter descriptions in MOF file.

Style changes to meet HQRM standards.

MSFT_xDnsClientGlobalSetting:

Renamed Localization strings file to be standard naming format.

Moved ParameterList into a new file (MSFT_xDnsClientGlobalSetting.data.psd1).

Style changes to meet HQRM standards.

Removed New-TerminatingError function because never called.

Converted to remove Invoke-Expression.

MSFT_xDnsConnectionSuffix:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xHostsFile:

Renamed Localization strings file to be standard naming format.

Style changes to meet HQRM standards.

Refactored for performance

Code now reads 38k lines in > 1 second vs 4

Now ignores inline comments

Added more integration tests

MSFT_xIPAddress:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xNetAdapterBinding:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xNetAdapterRDMA:

Renamed Localization strings file to be standard naming format.

Style changes to meet HQRM standards.

MSFT_xNetBIOS:

Renamed Localization strings file to be standard naming format.

Style changes to meet HQRM standards.

MSFT_xNetConnectionProfile:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xNetworkTeam:

Style changes to meet HQRM standards.

MSFT_xNetworkTeamInterface:

Updated integration tests to remove Invoke-Expression.

Style changes to meet HQRM standards.

MSFT_xRoute:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xFirewall:

Converted to remove Invoke-Expression.

xPSDesiredStateConfiguration 5.2.0.0

xWindowsProcess

Minor updates to integration tests because one of the tests was flaky.

xRegistry:

Added support for forward slashes in registry key names. This resolves issue 285.

xSqlServer 5.0.0.0

Improvements how tests are initiated in AppVeyor

Removed previous workaround (issue 201) from unit tests.

Changes in appveyor.yml so that SQL modules are removed before common test is run.

Now the deploy step are no longer failing when merging code into Dev. Neither is the deploy step failing if a contributor had AppVeyor connected to the fork of xSQLServer and pushing code to the fork.

Changes to README.md

Changed the contributing section to help new contributors.

Added links for each resource so it is easier to navigate to the parameter list for each resource.

Moved the list of resources in alphabetical order.

Moved each resource parameter list into alphabetical order.

Removed old text mentioning System Center.

Now the correct product name is written in the installation section, and a typo was also fixed.

Fixed a typo in the Requirements section.

Added link to Examples folder in the Examples section.

Change the layout of the README.md to closer match the one of PSDscResources

Added more detailed text explaining what operating systemes WMF5.0 can be installed on.

Verified all resource schema files with the README.md and fixed some errors (descriptions was not verified).

Added security requirements section for resource xSQLServerEndpoint and xSQLAOGroupEnsure.

Changes to xSQLServerSetup

The resource no longer uses Win32_Product WMI class when evaluating if SQL Server Management Studio is installed. See article kb974524 for more information.

Now it uses CIM cmdlets to get information from WMI classes.

Resolved all of the PSScriptAnalyzer warnings that was triggered in the common tests.

Improvement for service accounts to enable support for Managed Service Accounts as well as other nt authority accounts

Changes to the helper function Copy-ItemWithRoboCopy

Robocopy is now started using Start-Process and the error handling has been improved.

Robocopy now removes files at the destination path if they no longer exists at the source.

Robocopy copies using unbuffered I/O when available (recommended for large files).

Added a more descriptive text for the parameter SourceCredential to further explain how the parameter work.

BREAKING CHANGE: Removed parameter SourceFolder.

BREAKING CHANGE: Removed default value “$PSScriptRoot….” from parameter SourcePath.

Old code, that no longer filled any function, has been replaced.

Function ResolvePath has been replaced with [Environment]::ExpandEnvironmentVariables($SourcePath) so that environment variables still can be used in Source Path.

Function NetUse has been replaced with New-SmbMapping and Remove-SmbMapping.

Renamed function GetSQLVersion to Get-SqlMajorVersion.

BREAKING CHANGE: Renamed parameter PID to ProductKey to avoid collision with automatic variable $PID

Changes to xSQLServerScript

All credential parameters now also has the type [System.Management.Automation.Credential()] to better work with PowerShell 4.0.

It is now possible to configure two instances on the same node, with the same script.

Added to the description text for the parameter Credential describing how to authenticate using Windows Authentication.

Added examples to show how to authenticate using either SQL or Windows authentication.

A recent issue showed that there is a known problem running this resource using PowerShell 4.0. For more information, see issue #273

Changes to xSQLServerFirewall

BREAKING CHANGE: Removed parameter SourceFolder.

BREAKING CHANGE: Removed default value “$PSScriptRoot….” from parameter SourcePath.

Old code, that no longer filled any function, has been replaced.

Function ResolvePath has been replaced with [Environment]::ExpandEnvironmentVariables($SourcePath) so that environment variables still can be used in Source Path.

Adding new optional parameter SourceCredential that can be used to authenticate against SourcePath.

Solved PSSA rules errors in the code.

Get-TargetResource no longer return $true when no products was installed.

Changes to the unit test for resource

xSQLServerSetup

Added test coverage for helper function Copy-ItemWithRoboCopy

Changes to xSQLServerLogin

Removed ShouldProcess statements

Added the ability to enforce password policies on SQL logins

Added common test (xSQLServerCommon.Tests) for xSQLServer module

Now all markdown files will be style checked when tests are running in AppVeyor after sending in a pull request.

Now all Examples will be tested by compiling to a .mof file after sending in a pull request.

Changes to xSQLServerDatabaseOwner

The example “SetDatabaseOwner” can now compile, it wrongly had a DependsOn in the example.

Changes to SQLServerRole

The examples “AddServerRole” and “RemoveServerRole” can now compile, it wrongly had a DependsOn in the example.

Changes to CONTRIBUTING.md

Added section “Tests for examples files”

Added section “Tests for style check of Markdown files”

Added section “Documentation with Markdown”

Added texts to section “Tests”

Changes to xSQLServerHelper

added functions

Get-SqlDatabaseRecoveryModel

Set-SqlDatabaseRecoveryModel

Examples

xSQLServerDatabaseRecoveryModel

1-SetDatabaseRecoveryModel.ps1

xSQLServerDatabasePermission

1-GrantDatabasePermissions.ps1

2-RevokeDatabasePermissions.ps1

3-DenyDatabasePermissions.ps1

xSQLServerFirewall

1-CreateInboundFirewallRules

2-RemoveInboundFirewallRules

Added tests for resources

xSQLServerDatabaseRecoveryModel

xSQLServerDatabasePermissions

xSQLServerFirewall

Changes to xSQLServerDatabaseRecoveryModel

BREAKING CHANGE: Renamed xSQLDatabaseRecoveryModel to xSQLServerDatabaseRecoveryModel to align with naming convention.

BREAKING CHANGE: The mandatory parameters now include SQLServer, and SQLInstanceName.

Changes to xSQLServerDatabasePermission

BREAKING CHANGE: Renamed xSQLServerDatabasePermissions to xSQLServerDatabasePermission to align wíth naming convention.

BREAKING CHANGE: The mandatory parameters now include PermissionState, SQLServer, and SQLInstanceName.

Added support for clustered installations to xSQLServerSetup

Migrated relevant code from xSQLServerFailoverClusterSetup

Removed Get-WmiObject usage

Clustered storage mapping now supports asymmetric cluster storage

Added support for multi-subnet clusters

Added localized error messages for cluster object mapping

Updated README.md to reflect new parameters

Updated description for xSQLServerFailoverClusterSetup to indicate it is deprecated.

xPDT helper module

Function GetxPDTVariable was removed since it no longer was used by any resources.

File xPDT.xml was removed since it was not used by any resources, and did not provide any value to the module.

Changes xSQLServerHelper moduled

Removed the globally defined $VerbosePreference = Continue from xSQLServerHelper.

Fixed a typo in a variable name in the function New-ListenerADObject.

Now Restart-SqlService will correctly show the services it restarts. Also fixed PSSA warnings.

xWebAdministration 1.17.0.0

Added removal of self signed certificate to the integration tests of xWebsite, fixes 276.

Added EnabledProtocols to xWebApplication.

Changed SSLFlags for xWebApplication to comma seperate multiple SSL flags, fixes 232.

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/2kuLdfe

#DIYS

0 notes

repwinpril9y0a1 · 7 years

Text

DSC Resource Kit Release January 2017

We just released the DSC Resource Kit!

The modules updated in this release are:

AuditPolicyDsc

xDismFeature

xExchange

xNetworking

xPSDesiredStateConfiguration

xSQLServer

xWebAdministration

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

A new version of xActiveDirectory was also released about two weeks ago with some bug fixes for xADDomain and xADDomainController.

Included in this Release

Module Name Version Release Notes AuditPolicyDsc 1.1.0.0

Added the AuditPolicyCsv resource.

xDismFeature 1.2.0.0

xDismFeature: Resource no longer includes the Source parameter when it is not specified

Converted appveyor.yml to install Pester from PSGallery instead of from Chocolatey.

xExchange 1.13.0.0

Fix function RemoveVersionSpecificParameters

xExchMailboxServer: Added missing parameters except these, which are marked as “This parameter is reserved for internal Microsoft use.”

xNetworking 3.2.0.0

Fixed typo in the example”s Action property from “Blocked” (which isn”t a valid

value) to “Block”

Added support for auto generating wiki, help files, markdown linting

and checking examples.

Added NetworkingDsc.ResourceHelper module based on copy from PSDscResources.

MSFT_xFirewall:

Cleaned up ParameterList table layout and moved into a new file

(MSFT_xFirewall.data.psd1).

Separated Localization strings into strings file.

Added standard help blocks to all functions to meet HQRM standards.

Added CmdletBinding attribute to all functions to meet HQRM standards.

Style changes to meet HQRM standards.

Fixed issue using CIDR notation for LocalAddress or RemoteAddress.

See GitHub issue.

Fixed integration tests so that values being set are correctly tested.

Added integration tests for Removal of Firewall rule.

Added NetworkingDsc.Common module to contain shared networking functions.

MSFT_xDNSServerAddress:

Separated Localization strings into strings file.

MSFT_xDefaultGatewayAddress:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xDhcpClient:

Separated Localization strings into strings file.

Fix parameter descriptions in MOF file.

Style changes to meet HQRM standards.

MSFT_xDnsClientGlobalSetting:

Renamed Localization strings file to be standard naming format.

Moved ParameterList into a new file (MSFT_xDnsClientGlobalSetting.data.psd1).

Style changes to meet HQRM standards.

Removed New-TerminatingError function because never called.

Converted to remove Invoke-Expression.

MSFT_xDnsConnectionSuffix:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xHostsFile:

Renamed Localization strings file to be standard naming format.

Style changes to meet HQRM standards.

Refactored for performance

Code now reads 38k lines in > 1 second vs 4

Now ignores inline comments

Added more integration tests

MSFT_xIPAddress:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xNetAdapterBinding:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xNetAdapterRDMA:

Renamed Localization strings file to be standard naming format.

Style changes to meet HQRM standards.

MSFT_xNetBIOS:

Renamed Localization strings file to be standard naming format.

Style changes to meet HQRM standards.

MSFT_xNetConnectionProfile:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xNetworkTeam:

Style changes to meet HQRM standards.

MSFT_xNetworkTeamInterface:

Updated integration tests to remove Invoke-Expression.

Style changes to meet HQRM standards.

MSFT_xRoute:

Separated Localization strings into strings file.

Style changes to meet HQRM standards.

MSFT_xFirewall:

Converted to remove Invoke-Expression.

xPSDesiredStateConfiguration 5.2.0.0

xWindowsProcess

Minor updates to integration tests because one of the tests was flaky.

xRegistry:

Added support for forward slashes in registry key names. This resolves issue 285.

xSqlServer 5.0.0.0

Improvements how tests are initiated in AppVeyor

Removed previous workaround (issue 201) from unit tests.

Changes in appveyor.yml so that SQL modules are removed before common test is run.

Changes to README.md

Changed the contributing section to help new contributors.

Added links for each resource so it is easier to navigate to the parameter list for each resource.

Moved the list of resources in alphabetical order.

Moved each resource parameter list into alphabetical order.

Removed old text mentioning System Center.

Now the correct product name is written in the installation section, and a typo was also fixed.

Fixed a typo in the Requirements section.

Added link to Examples folder in the Examples section.

Change the layout of the README.md to closer match the one of PSDscResources

Added more detailed text explaining what operating systemes WMF5.0 can be installed on.

Verified all resource schema files with the README.md and fixed some errors (descriptions was not verified).

Added security requirements section for resource xSQLServerEndpoint and xSQLAOGroupEnsure.

Changes to xSQLServerSetup

The resource no longer uses Win32_Product WMI class when evaluating if SQL Server Management Studio is installed. See article kb974524 for more information.

Now it uses CIM cmdlets to get information from WMI classes.

Resolved all of the PSScriptAnalyzer warnings that was triggered in the common tests.

Improvement for service accounts to enable support for Managed Service Accounts as well as other nt authority accounts

Changes to the helper function Copy-ItemWithRoboCopy

Robocopy is now started using Start-Process and the error handling has been improved.

Robocopy now removes files at the destination path if they no longer exists at the source.

Robocopy copies using unbuffered I/O when available (recommended for large files).

Added a more descriptive text for the parameter SourceCredential to further explain how the parameter work.

BREAKING CHANGE: Removed parameter SourceFolder.

BREAKING CHANGE: Removed default value “$PSScriptRoot….” from parameter SourcePath.

Old code, that no longer filled any function, has been replaced.

Function ResolvePath has been replaced with [Environment]::ExpandEnvironmentVariables($SourcePath) so that environment variables still can be used in Source Path.

Function NetUse has been replaced with New-SmbMapping and Remove-SmbMapping.

Renamed function GetSQLVersion to Get-SqlMajorVersion.

BREAKING CHANGE: Renamed parameter PID to ProductKey to avoid collision with automatic variable $PID

Changes to xSQLServerScript

All credential parameters now also has the type [System.Management.Automation.Credential()] to better work with PowerShell 4.0.

It is now possible to configure two instances on the same node, with the same script.

Added to the description text for the parameter Credential describing how to authenticate using Windows Authentication.

Added examples to show how to authenticate using either SQL or Windows authentication.

A recent issue showed that there is a known problem running this resource using PowerShell 4.0. For more information, see issue #273

Changes to xSQLServerFirewall

BREAKING CHANGE: Removed parameter SourceFolder.

BREAKING CHANGE: Removed default value “$PSScriptRoot….” from parameter SourcePath.

Old code, that no longer filled any function, has been replaced.

Function ResolvePath has been replaced with [Environment]::ExpandEnvironmentVariables($SourcePath) so that environment variables still can be used in Source Path.

Adding new optional parameter SourceCredential that can be used to authenticate against SourcePath.

Solved PSSA rules errors in the code.

Get-TargetResource no longer return $true when no products was installed.

Changes to the unit test for resource

xSQLServerSetup

Added test coverage for helper function Copy-ItemWithRoboCopy

Changes to xSQLServerLogin

Removed ShouldProcess statements

Added the ability to enforce password policies on SQL logins

Added common test (xSQLServerCommon.Tests) for xSQLServer module

Now all markdown files will be style checked when tests are running in AppVeyor after sending in a pull request.

Now all Examples will be tested by compiling to a .mof file after sending in a pull request.

Changes to xSQLServerDatabaseOwner

The example “SetDatabaseOwner” can now compile, it wrongly had a DependsOn in the example.

Changes to SQLServerRole

The examples “AddServerRole” and “RemoveServerRole” can now compile, it wrongly had a DependsOn in the example.

Changes to CONTRIBUTING.md

Added section “Tests for examples files”

Added section “Tests for style check of Markdown files”

Added section “Documentation with Markdown”

Added texts to section “Tests”

Changes to xSQLServerHelper

added functions

Get-SqlDatabaseRecoveryModel

Set-SqlDatabaseRecoveryModel

Examples

xSQLServerDatabaseRecoveryModel

1-SetDatabaseRecoveryModel.ps1

xSQLServerDatabasePermission

1-GrantDatabasePermissions.ps1

2-RevokeDatabasePermissions.ps1

3-DenyDatabasePermissions.ps1

xSQLServerFirewall

1-CreateInboundFirewallRules

2-RemoveInboundFirewallRules

Added tests for resources

xSQLServerDatabaseRecoveryModel

xSQLServerDatabasePermissions

xSQLServerFirewall

Changes to xSQLServerDatabaseRecoveryModel

BREAKING CHANGE: Renamed xSQLDatabaseRecoveryModel to xSQLServerDatabaseRecoveryModel to align with naming convention.

BREAKING CHANGE: The mandatory parameters now include SQLServer, and SQLInstanceName.

Changes to xSQLServerDatabasePermission

BREAKING CHANGE: Renamed xSQLServerDatabasePermissions to xSQLServerDatabasePermission to align wíth naming convention.

BREAKING CHANGE: The mandatory parameters now include PermissionState, SQLServer, and SQLInstanceName.

Added support for clustered installations to xSQLServerSetup

Migrated relevant code from xSQLServerFailoverClusterSetup

Removed Get-WmiObject usage

Clustered storage mapping now supports asymmetric cluster storage

Added support for multi-subnet clusters

Added localized error messages for cluster object mapping

Updated README.md to reflect new parameters

Updated description for xSQLServerFailoverClusterSetup to indicate it is deprecated.

xPDT helper module

Function GetxPDTVariable was removed since it no longer was used by any resources.

File xPDT.xml was removed since it was not used by any resources, and did not provide any value to the module.

Changes xSQLServerHelper moduled

Removed the globally defined $VerbosePreference = Continue from xSQLServerHelper.

Fixed a typo in a variable name in the function New-ListenerADObject.

Now Restart-SqlService will correctly show the services it restarts. Also fixed PSSA warnings.

xWebAdministration 1.17.0.0

Added removal of self signed certificate to the integration tests of xWebsite, fixes 276.

Added EnabledProtocols to xWebApplication.

Changed SSLFlags for xWebApplication to comma seperate multiple SSL flags, fixes 232.

How to Find Released DSC Resource Modules

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 DSC modules are also listed as submodules of the DscResources repository in the xDscResources folder.

How to Contribute

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

Questions, comments?

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

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

#DIYS

0 notes

techyblogger · 2 years

Photo

Directly target your competitors' customers & boost your conversions (Tuwio Launch) https://www.reddit.com/r/SEO/comments/qm7npx/directly_target_your_competitors_customers_boost/

Hey everyone,

Sorry for the long wall of a post, but we're so excited, and Tuwio is now launched!

You can contact me here by sending a PM, or just send us an email at [email protected] for any questions, requests or to start your journey with us.

Best to you all!

submitted by /u/Ontealdon [link] [comments] November 04, 2021 at 05:17AM

0 notes