I'm attempting to use NuGet powershell cmdlets mentioned here.
I'm having a problem with the fact that I use VS2015 and my machines NuGet package source is pointing to "https://api.nuget.org/v3/index.json", but the powershell cmdlets only work when I specify a source of "http://www.nuget.org/api/v2/".
I also am missing the cmdlets that only exist in v3.
How do I upgrade my powershell nuget version?
Either a powersurge or something caused our router's configuration to get wiped, and our last backup was before the wireless network was setup.
We have not been able to reconfigure the wireless since then, so was curious if anyone here would be able to determine what configuration is needed.
We are using a Cisco 851W running 12.4(15)T9
We would like to use WPA encryption, and have it on the same network as the rest of the office network.
Config file is below:
User Access Verification
Building configuration...
Current configuration : 3857 bytes
!
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
no service dhcp
!
hostname BOB
!
boot-start-marker
boot-end-marker
!
enable secret 5 *********************
!
no aaa new-model
!
!
dot11 syslog
no ip source-route
!
!
ip cef
no ip bootp server
ip domain name BOB.com
ip name-server 61.11.1.1
ip name-server 61.11.1.2
!
!
!
username BOBB privilege 15 password 7 *************************
!
!
archive
log config
hidekeys
!
!
ip tcp synwait-time 10
!
!
!
interface FastEthernet0
no cdp enable
!
interface FastEthernet1
no cdp enable
!
interface FastEthernet2
no cdp enable
!
interface FastEthernet3
no cdp enable
!
interface FastEthernet4
description WAN Connection$ETH-WAN$
ip address 61.11.1.14 255.255.254.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
no cdp enable
!
interface Dot11Radio0
no ip address
shutdown
!
encryption mode ciphers tkip
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0
54.0
station-role root
no cdp enable
!
interface Dot11Radio0.1
encapsulation dot1Q 1 native
no cdp enable
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
!
interface Dot11Radio0.20
ip access-group Guest-ACL in
no cdp enable
!
interface Vlan1
description Internal Network
ip address 192.168.2.60 255.255.255.0
ip nat inside
ip nat enable
ip virtual-reassembly
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 61.11.2.14
!
ip http server
no ip http secure-server
ip nat inside source list 1 interface FastEthernet4 overload
!
ip access-list extended Guest-ACL
deny ip any 192.0.0.0 0.0.0.255
permit ip any any
!
access-list 1 permit 192.0.0.0 0.0.0.255
access-list 100 remark SDM_ACL Category=2
access-list 100 permit ip 192.0.0.0 0.0.0.255 any
no cdp run
!
control-plane
!
!
We have a server that we want our users to be able to remote into from within the office, but only a -few- (administrators) should be able to login from outside the office.
Currently, anyone who can remote into the desktop, has the ability to remote in from outside the office.
Is there a way to restrict remote desktop permissions by source of login?
We have an issue where some of our clients attempt to login to our system using a / instead of a \ for the domain.
This ends up with them attempting to login as
computername\domain/username
Also if they forget the domain part they end up attempting to login as
computername\username
Is there a way to setup a computer so that any logins to it from remote desktop\remoteapp default to a domain username, rather than a local computer username?
Would be much simpler to have our users simply type in their username.
Even though training them to use domain\username is simple, trying to do phone support for when they did a forward slash instead of a backslash has become a nightmare.
We have customers using our software via Remote App.
We have given them two options, using the .rdp file link we send them, or logging into the RDWeb and logging in that way.
We just recently discovered that the RDWeb has never worked (we only tested internally).
We are using an external port forwarding on a non-standard Remote Desktop port, to forward internally to the standard port of 3389 for the .rdp files.
My belief is that when using the Web Access, it is attempting to connect to the standard port rather than our port forwarded port, even though when I generated the .rdp file I specified the external port.
I believe this because I realize I never set a port to use for the RDWeb links.
Is there a way to configure what port the RDWeb links use?
We are using Windows Server 2008 R2
We made the mistake of Delegating Control over an OU to a user rather than a group.
We would like to correct this by removing the user from the OU's delegated control, but can't find where to modify this.
We can't even find the list of users who have received delegate control over the OU.
How do we get to this in Active Directory?
On some Remote Desktop servers, when two people login with the same username, it creates two sessions.
On other Remote Desktop servers, it kicks the first person off, and the second person takes over the session.
Where is the setting to determine this behavior?
We are trying to setup a server so that each user only has 1 session, but they end up logging into another session occasionally when they have network issues.
We use multiple servers, some are 2003, some are 2008, would be nice to know if the way this was configured differs on each as well.
Full Error Message:
System.Security.SecurityException: Request for the permission of type System.Web.AspNetHostingPermission, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed.
OS: Windows Server 2008 R2.
Web Server: IIS 7 with IIS 6 compatibility & metabase installed.
.NET: One website running fine under 2.0, this website is in 1.1
A common solution I've found is when the problem relies on files being on a shared network drive. This is not the case, all website files are on the C: drive of the server.
The ASP.NET 1.1 site did work fine on Windows 2003, however moving the site over to the new server has caused this issue.
All the files are accessible by the Web Service account and system accounts via the Windows File Security permissions.
In the site web.config under <system.web> we have:
<trust level="Full" />
3rd party libraries referenced in the bin folder:
DynamicPDF.Generator.dll DynamicPDF.Merger.dll EeekSoft.Web.PopupWin.dll NetSpell.SpellChecker.dll TTWebVBVS.dll
I'm at a loss as to what could be the issue, my intuition says the <trust level="Full" /> should have solved this, but it obviously hasn't.
If anyone has any ideas how this issue could be solved, I would appreciate it!
I found the following question, with a similar premise, however the answer to the question, was the question rephrased as a statement!
RemoteApp Prevent User from Running Remote Desktop
How do I allow RemoteApp but disallow Remote Desktop? In order to allow remote app, I'm seemingly having to add the users to the "Remote Desktop Users" group. This allows Remote Desktop.
I tried using the "TS Web Access Computers" group, however this does not give them the authority to run RemoteApp.
Where is the configuration to disable Remote Desktop, while leaving RemoteApp capabilities intact?
Simple question, I've been attempting to read through the MSDN and Googling, however I'm not finding anything that confirms yes or now.
MSDN gives a walk through for Server 2008, but Project Server 2007 came out before 2008, so I would imagine it would work on 2003. Just have no confirmation of it.
Client is creating a server that will be running our website and dual purposed to act as a print server.
We're trying to determine if Server 2008 Web Edition supports being a print server, however the comparison chart I found here only mentions Internet Print Client.
Unfortunately I work at a software company, so no one knows, and Microsoft's feature comparison isn't being incredibly helpful.
If Web Edition does not support Print Server, what is the recommended edition for a Web and Print server machine?
I have a client in the US that wants all time displayed as military time, but everything else is supposed to be US Culture.
In my global.asax I am creating a copy of the US culture and applying the GB time display to create a US culture with Military time.
Reason I am doing this is I could not find a culture capable of it, however if anyone knows, that would be great.
The problem I am running into, is when we deploy the website to IIS (version 6), it all reverts back seemingly to US culture.
Looking up how to change the culture, I found the setting in ASP.NET Tab -> Edit Configuration -> Application Tab
Default value is af-ZA.
There seems to be no option to disable this overriding of culture, and I don't believe af-ZA is right anyways?
Is there a way to prevent IIS from overriding a culture programmatically set in ASP.NET?
Note: Asking here since I'm looking for server side solution, not programming one. Thanks!
The system I am working on started to randomly reboot, thinking it was a harddrive error (we've had two machines fail due to this already), I rebooted the computer to run chkdsk.
Now the problem is that waiting the 1.5 hours for CHKDSK to complete, causes it to reboot without finishing, and hitting any key to skip CHKDSK blue screens with PAGE_FAULT_IN_NONPAGED_AREA.
Booting into safemode hangs on AGP40.sys, but booting the computer normally before I tried to do CHKDSK worked until it decided it was time to reboot itself.
Anyways, my goal is to simple disable the automatic CHKDSK on bootup. While speculations as to the root cause of this issue is welcome, the only thing I'm currently concerned with is getting the machine up temporarily.
And with CHKDSK running at bootup causing a crash, that is difficult.
I have learned how to do a LoadHive, however I have no idea which registry I file I need to load from C:\Windows\System32\Config\ nor where in that file I can load it from.
I currently have the harddrive in another machine, so I can do a loadhive, or do some config file modifications if necessary.
Side Note: Hardware is fine, moved harddrive to another machine and still fails to boot for the same reasons (while that machine boots just fine with it's own harddrive).