Unrecognized Credential Entry in "Windows PowerShell credential required" form

Hello,
I opened a PowerShell session and typed in: $Credential = Get-Credential,
As I was about to enter my credentials, just out of curiosity I clicked on the down arrow in the User Name field and noticed an unrecognized entry. The user name was " @@Stuff#-BTTB " where Stuff is a 22 character long
alpha-numeric string; otherwise the same.
This user name doesn't appear in the Credential Manager. OS is Windows 8.1.
Should I be worried?
What can I do to look into this further?
Thanks in advance!
Amendment:
Noticed the user name of a credential I had used recently didn't appear in the drop-down, so I was incorrect in thinking the list of user names reflected the history of user names used. I am curious where these credentials (identifies(?)) are
being pulled from though?

I have serveal working computers, out of curiosity, I ran the powershell cmd, and scroll down the listed username in the pop-up, I also find the similiar credentials @@....#...around the computers, but go through the credential manager and certificate
manager and unable find the credential. I can make a promise that my system is not infected by some malware,so in my opinion, it should be created by the system itself without our notice, anyway, then system is to complex for us to understand, I just
leave it there.

Similar Messages

[Forum FAQ] Introduce Windows Powershell Remoting

This article will introduce three methods of Windows Powershell Remoting:
Method 1: WMI
Remoting Cmdlet: Get-WMIObject
Protocols: WMI/RPC/DCOM
Port: Random port
Data Encryption: Clear text
Note: No need of the WinRM’s installation and configuration
Method 2: PowerShell Remoting Commands
Remoting Cmdlet: Invoke-Command
Protocols: HTTP (wsman), MIME, SOAP, XML
Port: 5985
Data Encryption: Encrypted
Note: Support any cmdlets in the parameter scriptblock, however, need the computer install WinRM, and also need to configure the WinRM on the remote computer.
Method 3: PowerShell Remoting Interactively
Remoting Cmdlet: Enter-PSSession
Protocols: HTTP (wsman), MIME, SOAP, XML
Port: 5985
Data Encryption: Encrypted
Note: Support any cmdlets, all cmdlets you type are executed as if they were typed on the console of the remote computer. However, need the computer install WinRM, and also need
to configure the WinRM on the remote computer.

2. Powershell remote in the same domain with WinRM installed: Invoke-Command, Enter-PSSession
2.1 PowerShell Remoting Commands: Invoke-Command
If you only have a couple of commands to execute on the remote computer in the same domain, you can use the
Invoke-Command cmdlet.
For example: Server1 want to remote manage Server2
1) Enable powershell remoting on Server2
Launch Windows Powershell as “Run as Administrator” on server2, and run:
Enable-PSRemoting –Force
Note:
In Server 2012 (but not Windows 8), PowerShell remoting is enabled by default, so you don't need to do anything.
2) Run invoke-command on server1
Invoke-Command -ComputerName server2 -Credential domain\username -ScriptBlock {get-process}
If the user account run with Powershell has the admin permission, there is no need to specify the credential parameter.
The script above will run the cmdlet “get-process” on server2, and a temporary connection will be built, the result returned to server1, and the connection broken.
If you want to run powershell script .ps1 file on server2, however, this script is stored on server1, you can achieve as below:
Invoke-Command -ComputerName server2 -Credential domain\username -FilePath d:\1.ps1
2.2 PowerShell Remoting Interactively: Enter-PSSession
To work interactively, use
Enter-PSSession to connect to a remote session, all the cmdlets you typed in your local console is executed on the remote system until you leave the remote session by using
Exit-PSSession.
After configure the WinRM on server2, you can run
enter-pssession on server1 (Figure 3):
Figure 3: remote with enter-pssession
2.3 Powershell remote with Pssession: New-Pssession
Whenever you use Windows PowerShell Remoting with the ComputerName parameter, a temporary session is created for you and used only for this particular command. Once the command
completes, the session is automatically closed.
If you start to access remote systems more often or would like to keep the session state, a more efficient way is to create sessions yourself and keep them around until you no longer
need them. To achieve this, instead of specifying the parameter computername, you can also specify Pssession in the Session parameter of the cmdlets
invoke-command and enter-pssession (Figure 4).
Figure 4: persistent session
If there is no need to use the Pssession, you can use the cmdlet
Remove-PSSession to close the session.

How to invoke windows powershell in soa bpel

Hi,
could anyone please let me know if we can invoke windows powershell from soa (bpel). if yes please share any helpful url for the same.
Thanks

Hi there,
you can use this discussion to see the Java code that is required in
order to get a PowerShell script executed from Java. Then you would have
to use the Java embedding in BPEL to call that code.
https://social.technet.microsoft.com/Forums/itmanagement/en-US/d32537bd-0aef-440e-8760-6b3085390c37/executing-powershell-script-via-java?forum=winserverpowershell
Hope this helps,
A.

How to uninstall Windows PowerShell

I attempted In-Place install of Vista SP2 over an exiting Vista SP2, then a message said I must uninstall Windows PowerShell. There is its short-cut in the program folder but there is no such entry in Add/Remove list.
How can I uninstall the Windows Powershell?

Also read:
http://technet.microsoft.com/en-us/library/dd351188.aspx
Uninstall Previous Versions of Windows PowerShell and Windows Remote Management
3 out of 28 rated this helpful
- Rate this topic
Applies to: Exchange Server 2010 SP2
Topic Last Modified: 2011-03-19
You need to uninstall previous versions of Windows PowerShell and Windows Remote Management (WinRM) before you can install Windows Management Framework, which includes Windows PowerShell 2.0 and WinRM 2.0. This procedure should be performed on computers
running Windows Vista, Windows Server 2008, Windows Server 2003, or Windows XP.
You don't need to perform this procedure on computers running Windows 7 or Windows Server 2008 R2. The current version of Windows Management Framework is already installed on these operating systems.
Looking for other management tasks related to Windows PowerShell and Windows Remote Management? Check out
Managing Exchange Management Shell Connections.
Note:
If you want to run remote Shell on a computer that already has Microsoft Exchange Server 2010 installed, you don't need to perform this procedure. Instead, for more information about how to open the Shell with the Exchange management tools installed, see
Open the Shell.
What Do You Want To Do?
Remove Windows PowerShell on Windows Vista
Remove Windows PowerShell on Windows Server 2008 with the built-in version of Windows PowerShell installed
Remove Windows PowerShell on Windows Server 2008 with a pre-release version of Windows PowerShell V2 installed
Remove WinRM on Windows Vista and Windows Server 2008
Remove Windows PowerShell on Windows Server 2003 and Windows XP
Remove WinRM on Windows Server 2003 and Windows XP
Remove Windows PowerShell on Windows Vista
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "PowerShell and WinRM installation" entry in the
Exchange and Shell Infrastructure Permissions topic.
In Control Panel, in Programs, open
Programs and Features.
Uninstall any instances of Windows PowerShell that appear in the installed programs list or the installed updates list. Previous versions may appear as
Windows PowerShell(TM) V2 if you have installed the Community Technology Preview (CTP) versions of Windows PowerShell v2. If Windows PowerShell v1 is installed, it might be listed as a Windows update with one of the following Knowledge Base
article numbers:
KB928439
KB923569
Note:
You might need to click the View installed updates link in the Tasks sidebar to view currently installed updates.
Remove Windows PowerShell on Windows Server 2008 with the built-in version of Windows PowerShell installed
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "PowerShell and WinRM installation" entry in the
Exchange and Shell Infrastructure Permissions topic.
Start Server Manager and navigate to Features.
Click Uninstall Features.
Select Windows PowerShell and follow the directions to uninstall.
Remove Windows PowerShell on Windows Server 2008 with a pre-release version of Windows PowerShell 2.0 installed
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "PowerShell and WinRM installation" entry in the
Exchange and Shell Infrastructure Permissions topic.
In Control Panel, in Programs, open
Programs and Features.
Uninstall any instances of Windows PowerShell that appear in the installed programs list or the installed updates list.
Note:
You might need to click the View installed updates link in the Tasks sidebar to view currently installed updates.
Remove WinRM on Windows Vista and Windows Server 2008
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "PowerShell and WinRM installation" entry in the
Exchange and Shell Infrastructure Permissions topic.
In Control Panel, in Programs, open
Programs and Features.
Uninstall any instances of Windows Remote Management that appear in the installed programs list or the installed updates list. WinRM might be listed as a Windows update with one of the following Knowledge Base articles numbers:
KB936059
KB950099
Note:
You might need to click the View installed updates link in the Tasks sidebar to view currently installed updates.
Remove Windows PowerShell on Windows Server 2003 and Windows XP
In Control Panel, open Add or Remove Programs.
Uninstall any instances of Windows PowerShell that appear in the installed programs list or the installed updates list. Windows PowerShell might be listed as a Windows update with the Knowledge Base article number KB926139.
Note:
You might need to select the Show updates box to view currently installed updates.
Remove WinRM on Windows Server 2003 and Windows XP
In Control Panel, open Add or Remove Programs.
Uninstall any instances of Windows Remote Management that appear in the installed programs list or the installed updates list. WinRM might be listed as a Windows update with the Knowledge Base article number KB936059.
Note:
You might need to select the Show updates box to view currently installed updates.
Other Tasks for Peace!
Devnullius
After you uninstall all previously installed versions of Windows PowerShell and WinRM, you need to install Windows Management Framework. For more information, see
Install Windows Management Framework.

Tech Tip of the Week: Windows Powershell CMDlets

This week’s tech tip is for all you Windows PowerShell users.If you’re using PowerShell, you may already know about CMDlets. If not, this post is sure to excite you, as CMDlets (pronounced “command-let”) are nifty commands that will ease the process of using
Powershell.
Here are 5 CMDlets to get you started:
1. Get-Recipient | Where {$_.EmailAddresses –match “[email protected]”}
This CMDlet will find an email address that is inside of the quotes.
2. (Get-Mailbox) | ForEach {Set-Mailbox $_.Identity –RetentionPolicy “Contoso-Policy”}
This CMDlet applies a single retention policy to all users.
3. Get-MSOLUser | Set-MSOLUser –PasswordNeverExpires $true
This sets all users passwords to never expire (Requires Azure Module)
4. (Get-Recipient) | ForEach {Add-RecipientPermission –identity $_.PrimarySMTPAddress –trustee [email protected] –AccessRights SendAs –Confirm:$Y}
This gives a single mailbox SendAs rights to all other recipients (groups, mailboxes, external contacts).
5. (Get-Mailbox) | ForEach {Enable-Mailbox –identity $_.PrimarySMTPAddress –Archive}
This CMdlet turns on archiving for all mailboxes
Try out these CMDlets and let us know what you think!

This week’s tech tip is for all you Windows PowerShell users.If you’re using PowerShell, you may already know about CMDlets. If not, this post is sure to excite you, as CMDlets (pronounced “command-let”) are nifty commands that will ease the process of using
Powershell.
Here are 5 CMDlets to get you started:
1. Get-Recipient | Where {$_.EmailAddresses –match “[email protected]”}
This CMDlet will find an email address that is inside of the quotes.
2. (Get-Mailbox) | ForEach {Set-Mailbox $_.Identity –RetentionPolicy “Contoso-Policy”}
This CMDlet applies a single retention policy to all users.
3. Get-MSOLUser | Set-MSOLUser –PasswordNeverExpires $true
This sets all users passwords to never expire (Requires Azure Module)
4. (Get-Recipient) | ForEach {Add-RecipientPermission –identity $_.PrimarySMTPAddress –trustee [email protected] –AccessRights SendAs –Confirm:$Y}
This gives a single mailbox SendAs rights to all other recipients (groups, mailboxes, external contacts).
5. (Get-Mailbox) | ForEach {Enable-Mailbox –identity $_.PrimarySMTPAddress –Archive}
This CMdlet turns on archiving for all mailboxes
Try out these CMDlets and let us know what you think!

[Forum FAQ]Solution for Windows PowerShell console font issue when changing system locale

Issue description
After changing Windows System Locale to another country, users cannot modify Windows PowerShell console font to Lucida after modifying the font settings. There is also a potential bug report in Microsoft connect:
https://connect.microsoft.com/PowerShell/feedback/details/806286/powershell-4-console-font-issue
Reason
In most situations, this problem is caused by system locale is changed to other countries from United States, such as Chinese, French, etc. Because of this change, the code page and font of Windows PowerShell console might be changed with system locale.
For Example, if change system locale to Chinese (Simplified China), Windows PowerShell console
(%systemdrive%\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools) properties would be changed like this:
Solution
To resolve this problem, please follow the steps below:
Access to the path below to find the shortcut of Windows PowerShell:
%systemdrive%\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools.
Right click Windows PowerShell and choose Properties.
Switch to Options, check if Current code page list there, if that it is, choose
437 (OEM-United States) and click Apply. Maybe you will encounter an
Access Deniedpop-up as the following picture. Then you need take ownership of current PowerShell File, switch to
Security Tab and obtain full control permission for current User Account.
Note: if Current code page was not list there, just leave alone
Options settings and switch to Font Tab.
Switch to Font Tab, choose the font you wished to use, click
Apply.
After the above settings, current Windows PowerShell console font should works as you wished.
Applies to
Windows PowerShell 3.0
Windows PowerShell 4.0
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Cause
This issue is due to the bootmgr file, we cannot use the bootmgr file of Windows 7 to find the Windows 8 Operating System files.
The Windows 7 bootmgr can indeed boot Windows 8.
This is on a BIOS system
https://www.youtube.com/watch?v=AVO5aeaKeeE
This is on a UEFI system
https://www.youtube.com/watch?v=g3-K6Fyobz0
The Windows 8 bootmgr partially loads Windows 8 before offering the boot menu. By choosing Windows 7, the system must do a reboot. Using the Windows 7 bootmgr, no reboot is required.
"Let them that don't want it have memories of not gettin' any." "Gratitude is riches and complaint is poverty and the worst I ever had was wonderful." Brother Dave Gardner. "Experience is what you get when you're looking for something
else." Sir Thomas Robert Deware

Efibootmgr & gummiboot replaced UEFI entry for Windows Boot Manager

TLDR
I am now in Windows 7 and dual boot with Arch is working fine.
But before I update Arch, I would like to understand what happened, as in why adding an efibootmgr entry for Arch replaced/deleted the Windows Boot Manager entry although I followed the BG.
The status of my UEFI boot menu was, before the installation of Arch:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
While working through the BG, I decided to use gummiboot=> https://wiki.archlinux.org/index.php/Be … #Gummiboot. So:
pacman -S gummiboot
gummiboot install
pacman -S efibootmgr
gummiboot install
[some error ocurred, as mentioned in red box]
efibootmgr -c -L "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi
nano /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 ro
[CTRL + X, Y, Enter]
exit
umount /mnt/{boot,home,}
reboot
I then saw a new list of the UEFI boot order:
Gummiboot
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
Chose Gummiboot and it brought up a gummiboot menu with entries
Arch Linux
Windows Boot Manager
EFI Shell something
Selected Arch Linux and it went to a message something along "boot device ' ' not found" and I was in a shell which was, I think, rootfs.
I rebooted via the button on my desktop and out the Arch Linux USB drive back. After mounting the partitions:
gummiboot remove
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
Now I booted into a black screen with white text which said something "Reboot and select proper Boot device"
=> Inserted Win 7 64-bit DVD, repaired the boot sector. Rebooted, saw I had these entries again:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
The boot into Windows worked fine. Rebooted, chrooted into my install again and:
efibootmgr
[0000: Arch Linux
[0001: Windows Boot Manager
[0003: AHCI HDJ...
[0003: AHCI ST...
efibootmogr -b 0 -B
Then I used the EFISTUB method:
efibootmgr -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdb3 ro initrd=/initramfs-linux.img"
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
On reboot, 'Windows Boot Manager' was again replaced by 'Arch Linux'.
=> Inserted Win 7 64-bit DVD, repaired the boot sector.
Rebooted, I have now Windows Boot Manager + Arch Linux and dual boot works now.
My questions:
What is going on with efibootmgr replacing/deleting the Windows entry? Is there something wrong with my UEFI menu?
In connection with 1., I would like to sync the EFISTUB Kernel (wiki entry) before I run pacman -Syu. Can I do that now?
Can I uninstall gummiboot now?
Last edited by jones (2013-07-11 12:30:55)

henrik wrote:So in light of your post, I decided to ditch EFISTUB + gummiboot and try out GRUB. Thanks for clearing it up a bit. Which is what confuses me a great deal more, as GRUB/gummiboot obviously do not meddle with Microsoft's EFI files. Right?
EFI relies on two things to boot:
Boot loader program files on the ESP (or occasionally elsewhere).
NVRAM entries pointing to the boot loader files.
Your own problems seem to be with the NVRAM entries, not with the boot loader files themselves. Unfortunately, managing those NVRAM entries has proven to be problematic because of bugs in specific EFI implementations, bugs in efibootmgr and other tools that manipulate the NVRAM entries, poor documentation, and other factors.
To answer your question, though, no boot loader should mess with another's files. Such things can happen, though. The number of bugs that cause Microsoft's boot loader (EFI/Microsoft/Boot/bootmgfw.efi) to be treated deferentially have provoked some tools to use it as a target location for other boot loaders. (Ubuntu's Boot Repair tool does this in a rather overzealous way. So does my own rEFInd installer script, but only under certain narrow circumstances.) Also, the EFI/BOOT/bootx64.efi file is a special case; it's the fallback bootloader that's used when NVRAM entries are missing or don't work, and various boot loader installation procedures place copies in that location, so it can be overwritten and could contain just about anything.
However, the whole thing happened again with GRUB. So I did the whole "repairing Boot problems" with the Windows DVD rescue thingy again and deleted all non-Microsoft files from the EFI partition, /dev/sda1.
Then I formatted / (root) and installed arch again and followed the Beginners' Guide which suggest mounting /dev/sda1/ to /mnt/boot (in contrast to the GRUB entry where the ESP should be mounted to /mnt/boot/efi).
I strongly advise against doing a complete re-installation just to overcome a boot loader problem. Instead, figure out what the problem is and fix it. Doing a complete re-installation is not likely to fix anything, and depending on precisely how you do it, you could end up with a more complex problem. The reason is that the re-installation is not likely to erase the NVRAM entries from the old installation, so you could find that you've got additional stray NVRAM entries. If you do happen to fix the problem by re-installing (say, because you selected a different installation option), you're not likely to know what changed to fix the problem, so you could end up in the same boat should you need to re-install again in the future.
But it did not show this line
Found Windows 7 (loader) on /dev/sda1
... how come??
I've given up trying to understand GRUB's configuration scripts. You could try creating an entry manually by editing /etc/grub.d/40_custom; or you could forget about using the GRUB scripts and create a hand-crafted grub.cfg; or you could forget about using GRUB at all. I'm not a fan of GRUB, so my personal choice is the final one.
So for all the headache and time ... should I delete the EFI partition and recreate it maybe? I think it's possible using the Windows 7 DVD.
But somehow using efibootmgr on my UEFI list somehow invalidated the Windows entry.
Reviewing your posts, it seems that you want to use the EFI stub loader directly, but you're having problems with that because when you add it to the NVRAM entries, Windows drops off your boot manager's boot options. The obvious solution to this problem is to forget about adding the EFI stub loader directly to the NVRAM entries, and instead add a boot manager that can handle either a Linux kernel or the Windows boot loader. (IMHO, this is the superior solution anyhow; I disagree with the Arch wiki's emphasis on using the EFI stub loader "raw.") It seems you were trying to do this with GRUB but had problems booting Windows. Earlier you tried gummiboot but had problems booting Linux. My suggestion is to either go back to gummiboot and fix its problem or try rEFInd. The "device not found" error you reported with gummiboot is usually caused by either a missing (or incorrectly-specified) initrd file or by an incorrectly-specified "root=" option passed to the kernel. Check those possitilities, and if you need help, report what happens in more detail. If necessary, take a digital photo of the screen and post it here. (Make sure it's legible, though!)
You can try rEFInd with minimal disk by using a CD-R or USB flash drive image. Boot with that and your NVRAM and ESP won't be affected at all. If you can get rEFInd working from the flash drive, you can then install it to your hard disk and it should continue working. Note that you probably won't be able to boot Linux directly from rEFInd with your current configuration without adding a "root=" specification to the kernel command line. You can do this by hitting F2 or Insert twice rather than launching Linux by pressing Enter. Alternatively, you can create a refind_linux.conf file in the directory that holds your kernel. That file's contents are described in the rEFInd documentation.

[Forum FAQ] How to find and replace text strings in the shapes in Excel using Windows PowerShell

Windows PowerShell is a powerful command tool and we can use it for management and operations. In this article we introduce the detailed steps to use Windows PowerShell to find and replace test string in the
shapes in Excel Object.
Since the Excel.Application
is available for representing the entire Microsoft Excel application, we can invoke the relevant Properties and Methods to help us to
interact with Excel document.
The figure below is an excel file:
Figure 1.
You can use the PowerShell script below to list the text in the shapes and replace the text string to “text”:
$text = “text1”,”text2”,”text3”,”text3”
$Excel
= New-Object -ComObject Excel.Application
$Excel.visible = $true
$Workbook
= $Excel.workbooks.open("d:\shape.xlsx")
#Open the excel file
$Worksheet
= $Workbook.Worksheets.Item("shapes")
#Open the worksheet named "shapes"
$shape = $Worksheet.Shapes
# Get all the shapes
$i=0
# This number is used to replace the text in sequence as the variable “$text”
Foreach ($sh in $shape){
$sh.TextFrame.Characters().text
# Get the textbox in the shape
$sh.TextFrame.Characters().text =
$text[$i++]
#Change the value of the textbox in the shape one by one
$WorkBook.Save()
#Save workbook in excel
$WorkBook.Close()
#Close workbook in excel
[void]$excel.quit()
#Quit Excel
Before invoking the methods and properties, we can use the cmdlet “Get-Member” to list the available methods.
Besides, we can also find the documents about these methods and properties in MSDN:
Workbook.Worksheets Property (Excel):
http://msdn.microsoft.com/en-us/library/office/ff835542(v=office.15).aspx
Worksheet.Shapes Property:
http://msdn.microsoft.com/en-us/library/office/ff821817(v=office.15).aspx
Shape.TextFrame Property:
http://msdn.microsoft.com/en-us/library/office/ff839162(v=office.15).aspx
TextFrame.Characters Method (Excel):
http://msdn.microsoft.com/en-us/library/office/ff195027(v=office.15).aspx
Characters.Text Property (Excel):
http://msdn.microsoft.com/en-us/library/office/ff838596(v=office.15).aspx
After running the script above, we can see the changes in the figure below:
Figure 2.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Thank you for the information, but does this thread really need to be stuck to the top of the forum?
If there must be a sticky, I'd rather see a link to a page on the wiki that has links to all of these ForumFAQ posts.
EDIT: I see this is no longer stuck to the top of the forum, thank you.
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing)

[Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.
Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force
Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
the memory via the PowerShell command below:
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.
You can get more information regarding Remote Troubleshooting by below link:
about_Remote_Troubleshooting
If you need further assistance, welcome to post your questions in the
RDS forum.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
ot process the request. It cannot determine the content type of the HTTP response from the destination comput
er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
many security groups or in my case because of the SidHistory attribute.
The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
If the keys does not exists you can create them, be sure to use the DWORD type.
I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

Windows 10 Error code: 0x80070570 at 68% "windows cannot install required files"

Trying to do a clean install from a USB flash drive and DVD. Same error each time at same location. (68%) I have removed all USB devices, Ran chkdsk and updated firmware on SSD.
Asus Sabertooth P67 BIOS 3602
i7-2600k 3.4GHz
24GB ram DDR3
500G SSD OCZ Vortex Sata 3
"Windows cannot install required files. The file may be corrupt or missing. Make Sure all files required for installation are available, and restart the installation.
Error code: 0x80070570"

Hi Covered,
Glad that you have resolved this issue.
Have a nice day!
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

'Windows cannot install required files' error while installing Vista SP1

I'm installing Vista Client SP1 on my Macbook pro and getting the following error:
Windows cannot install required files. Make sure all files required for installation are available, and restart the installation.
Almost exactly as described in this KB article: http://support.microsoft.com/kb/930984/ except my error code is 0x80070017. I'm double-checked CRC on my dvd to ensure it's not corrupt. Also I've previously successfully installed Vista SP1 from the SAME DVD on a different Mac Leopard (desktop)
Any ideas? This is a new Macbook pro, just got it yesterday. Could be DVD drive issue?
Thanks!

Did you get far enough to delete the FAT partition BootCamp created, so you could create a new NTFS one?
http://support.microsoft.com/kb/933925
or this:
http://discussions.apple.com/thread.jspa?threadID=1464025&tstart=0

HT2480 I have a new windows 8 laptop required at work and want to sync my iphone 5 contacts, calendar, etc with OUtlook. How?

I have a new windows 8 laptop required at work and want to sync my iphone 5 with outlook. We do not have an exchange network

Have a look at this: http://support.apple.com/kb/DL1455

Using WEBDAV in a Windows PowerShell script

Hello,
I am trying to write a Windows PowerShell script to copy a file from my SharePoint site to a DB repository folder using a WEBDAV link. I am not getting it to work.
When I copy from SharePoint to SharePoint it works. I have used my credentials on the script which has the authorizations but it still isn't working. The response error is a 500 Internal Server error.
Any ideas?
Has anyone done this before?
Thanks,
Matt

This is not a solution but more an extra tool to help you find a solution....
You could download and install the Portal Drive to see what actions/commands are used to communicate via webdav to the KM repository.
Cheers,
B

Connect via Windows Powershell in SCCM 2012 CONSOLE (with PowerShell 4.0 installed)

Hi,
When trying to "Connect via Windows Powershell" in the SCCM 2012 console, I get the message that Powershell 3.0 is not installed... (which actually isn't installed, we have PS4.0 installed). Do we need to install PS3.0 also to get it working
or is there a workaround? Connecting manually to the site via Powershell 4.0 (Get-Psdrive -psprovider CMSITE) works like a charm.
Regards,
WiM

Hi,
I have installed WMF 4.0 on Windows Server 2008 R2 sp1, it works fine.
Please try to use "$PSVersionTable" to confirm Powershell version is 4.0. At first, I forgot to install Microsoft .NET Framework 4.5, then the console gave me the message that Powershell 3.0 is not installed.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Errors "A media driver your computer needs is missing." or "Windows cannot install required files" upon attempting to install Windows 10 TP build 10041 64-bit

I'm attempting to install Windows 10 TP build 10041 [64-bit]
I am currently being prevented from installing by a "A media driver your computer needs is missing." error, which occurs fairly early in the process. I've interpreted further text in the message as a suggestion that it's a DVD, USB or some other
similar driver issue. However, as I've been able to attempt each install through booting from DVD and USB, I'm not convinced this is the issue.
I'm currently installing to a 128Gb SSD drive. I have installed Windows 10 TP on my laptop's SSD with no issues.
On a few occasions the installation has continue with the installation, and then failed at about 6% with the following error:
"Windows cannot install required files. Make sure all files required for installation are available, and restart the installation. Error code 0x8007045D". I have not removed the installation USB or DVD.
I did not have this issue when installing build 9841, so am currently assuming this is an issue with build 10041.
Apologies if this query has been posed before, a search did not show up this issue.
Any advice would be greatly appreciated.

Hi Michael,
Thanks for trying to assist!
I attempted removing/deleting partitions and formatting the SSD as part of the install process. I have also tried installing via USB and DVD with the same issues.
As part of the troubleshooting, I attempted to install a different OS. I was able to successfully install Linux Mint 17.1 with no issues. This further solidifies my impression this is an issue with Windows.
I will try a different USB port, appreciate the suggestion, didn't think it would make a different given the various methods already attempted.

Unrecognized Credential Entry in "Windows PowerShell credential required" form

Similar Messages

Maybe you are looking for