Server 2012 Disable Uac
Janoc Florez
We have a generic VS which receives all of the traffic for a certain IP address + port 443. We have applied the ProxyPass iRule which distributes the connections to the correct pool based on the URL.
The pool member is using a non standard port over the HTTP protocol so when the BIG-IP device is establishing its connection to the pool member it obviously does not work since it's communicating over HTTPS.
I have been trying to turn off the Server SSL profile by using iRules but I don't seem to get it to work. I have used the examples found in the SSL::disable article and I have the following examples that I have tried:
Example 3 will probably turn off ServerSSL entirely but either way it did not work. I'm starting to guess that the ProxyPass iRule is conflicting with my own iRule but I don't have enough iRule knowledge to determine that.
@ppoorab1 There isn't any settings or functionality to disable just scheduler entirely on the server as the underlying functionality is used for all workflows run by the server. However, you can take a couple approaches to preventing or limiting scheduled jobs depending on your specific needs, configuration, and what version you are running currently. If you are on 11.0 or higher and using exclusively Gallery for scheduling a Curator can go in and disable the ability to schedule workflows. Then edit each scheduled workflow setting them to disabled. Once they are tested the Curator can then re-enable each schedule as needed and the ability for users to schedule workflows. I think this is the best option if it is available to you.
If you aren't on 11.0+ or if you are still scheduling workflows directly from Designer you can achieve a similar result by editing each schedule from within Designer and setting the frequency to Once. This will update the schedule so that the workflows will no longer run on a recurring basis. However, anyone with access to schedule in this manner would be able to edit the schedule to set it back to a recurring state or create new schedules.
A final option would be to disable the worker(s) entirely. This can be done via the Alteryx System Settings by selecting Custom under Setup Type and unchecking the Enable Worker option. Disabling the workers will prevent the server from running any workflow at all. This would include scheduled workflows, user run workflows, workflows run via Gallery API request, and workflow validations when saving workflows to Gallery. Any workflows sent to the queue while the worker(s) are disabled will sit in queue until the worker(s) are re-enabled. This can lead to a very large backlog of pending tasks, and could make adequately testing the workflows difficult.
@ppoorab1 Backing up the database first is an excellent idea, and would give you the opportunity to roll back to your current version. For information on backup best practices and procedures please refer to the Alteryx Server Backup & Recovery knowledge articles. Since none of the options presented are viable for you I would proceed is as follows:
Keep in mind though that this is only viable if you are using MongoDB as your persistence layer. Since you are currently using server without Gallery it is possible that you are using SQLite instead. If this is the case you will have to start with a blank database in order to deploy Gallery as MongoDB is required for Gallery, and there isn't a migration tool to convert from SQLite to MongoDB. This does have the advantage of letting you test on a blank database without have to do repeated backup/restore processes. Just stop the service and backup the entire persistence folder (default: C:\ProgramData\Alteryx\Service\Persistence). Then reconfigure the service to use MongoDB, upgrade to 11.7, and test. If everything goes well your users would just need to re-upload their production workflows and re-schedule them once testing is complete.
I am looking for a way to disable WSD on Server 2012 and Server 2012 R2. Basically, a number of our printers on a number of our print server have decided that using this bloody service is better than using the TCP/IP ports they were assigned, and they are changing themselves over to WSD ports which results in users being unable to print to these printers.
I'd like a way to disable this service (and only this service) at the print server, because any of the other options involve a lot more work than I'd like (2, 3) or have undesirable side-effects (1). Does anyone know of a way to do this?
While WSD printers are shown in Add Printer window, and it seems you can add them, WSD ports are never created, and the WSD driver for printer is not installed. All criteria satisfied. Verified in Windows Server 2012 R2.
1 Drawback: You should rename the 3 files back to their original names before doing any Windows Updates related to printing or WSD. And then change them back to .bak after patch installed successfully.
Install the printer manually through Devices and Printers to the network. Select the option to "Add a printer using a TCP/Ip address or hostname. In the next window, make sure to change the the Device Type option to TCP/IP Device and NOT the Auto Detect option (which is generally the default). Enter the IP address of the printer and click Next. Finish the install as normal from this point. This should resolve this issue.
I found a registry entry for my WSD port under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Monitors\WSD Port\Ports. There was a key named the same as the port. Once the offending key was deleted, the printer stopped auto-assigning itself to that port.
I configured SSL on ArcGIS Server 10.3.1 a couple of weeks ago due to another application. I thought everything was working ok but later I realised that I couldnt log in to ArcGIS server manager anymore, and my WMS Services were not working. I would now like to disable SSL but cannot configure it. When I try to delete my SSL certificate I get the error code 500 - Standard certificate annot be deleted. I have disables SSL on IIS, but this doesnt help.
There is a third recovery mode not mentioned above. The recovery mode ultimately determines how large the LDF files become and how ofter they are written to. In cases where you are going to be doing any type of bulk inserts, you should set the DB to be in "BULK/LOGGED". This makes bulk inserts move speedily along and can be changed on the fly.
In the spirit of adding to the conversation about why someone would not want an LDF, I add this: We do multi-dimensional modelling. Essentially we use the DB as a large store of variables that are processed in bulk using external programs. We do not EVER require rollbacks. If we could get a performance boost by turning of ALL logging, we'd take it in a heart beat.
Very few people have a need to run their databases in the Full recovery model. The only point in using the Full model is if you want to backup the database multiple times per day, and backing up the whole database takes too long - so you just backup the transaction log.
The transaction log keeps growing all day, and you keep backing just it up. That night you do your full backup, and SQL Server then truncates the transaction log, begins to reuse the space allocated in the transaction log file.
In SQL Server 2000 or in SQL Server 2005, the "Simple" recovery model is equivalent to "truncate log on checkpoint" in earlier versions of SQL Server. If the transaction log is truncated every time a checkpoint is performed on the server, this prevents you from using the log for database recovery. You can only use full database backups to restore your data. Backups of the transaction log are disabled when the "Simple" recovery model is used.
With this setup webpack dev server opens the initial page as localhost:9005/webpack-dev-server/ with auto reload on (iframe mode). When I set inline to true then it opens localhost:9005 and auto reload is still on (inline mode => websockets).
I own a TL-WA1201 Access Point and it appears to have a DHCP server function. I would like to disable this DHCP server as my router is providing that function (and the Wireless network and wired network are on the same subnet).
Looks like some sort of issue with the LAN Settings or using DHCP and somehow getting the mask set incorrectly is causing the initial problem. Not really sure if this is a workaroudn or a solution. Probably a workaround.
I've used an Ip address outside the range of my DHCP server on the router but still within the 192.168.1.0/27 range to avoid a clash and am happy to work as it is. The image below attempts to capture some of the success in saving the settings after switching to static IP address and setting the correct subnet mask.
I can think of a use case where the DHCP server is not on a router but the router is using IP helpers to reach out to DHCP server sitting on a different box/network. I wonder if auto will work in this case?
Not sure if I'd recommend this product without the ability to disable the DHCP server completely. Let's just say it's lucky my current use case is supported by auto in that it doesn't serve out IP addresses as my router on the same network/subnet is doing it. But there are other use cases which might result in the DHCP server becoming active when it shouldn't be. Like on a multi subnet network with DHCP IP helpers perhaps. Testing required to check this scenario, but rather just have the ability to switch off the DHCP server on the WAP completely than faff around with the auto setting hoping it behaves.
I've tried a hardware reset and then connected to the admin page on the WAP and tried to disable the DHCP server. Same issue. A message appears stating Failed when trying to disable the DHCP function on WA1201.
4a15465005