Hi,

Granting shared/security permission could be tricky sometimes.

I need a guidance to do this properly. Share permission layout can be described as:

Scenario:

User is mapped to the share "\\server\ShareA" as W: drive via logon script.

So they see W: drive in their Computer.

Let say I'm grouping users into AD Group named "DOMAIN\Dept-A", what kind of permission should be assigned to the share and/or Security tab for this folder, so the user can see W: drive, and have Read+Write permission on their dept. folder"Dept-A"?

W: drive should be accessible across departments groups e.g "DOMAIN\Dept-B" and "DOMAIN\Dept-C" too, but they should be allowed to list folders in W: drive but denied access on "Dept-A" folder?

---Pat

I have a VPS running WS 2016 (not AD). I host some .net applications on the machine and machine has own DNS Server with two dedicated public IP. Everything was fine without RRAS configuration, but I needed a VPN service and added one virtual NIC to configure RRAS. While RRAS active, I cannot reach my VPS via Remote Desktop, also my host sites are unavailable due name resolution error. My RRAS configuration as follows:

Appreciate for help.

We are running an engineering network hanging off the third burb of our hosting organization's Cisco ASR.  The ASR is a stratum 2 device having synced time with their GPS Time Server. 

We have configured our core Cisco switch to pull time from the ASR and to make itself available as a Stratum 3 time source for our network. I have had no issues with the other infrastructure devices syncing.  I configured our PDC emulator to use the core node using the following command:

w32tm /config /manualpeerlist:10.1.1.164 /syncfromflags:manual /reliable:yes /update

The immediate result was Time-Service Event ID 37 - "The time provider NtpClient is currently receiving valid time data from 10.1.1.164 (ntp.m|0x0|0.0.0.0:123->10.1.1.164:123)."

However, four minutes later, it was followed up with a Time-Service Event ID 47 warning - "Time Provider NtpClient: No valid response has been received from manually configured peer 10.1.1.164 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable."

Obviously, since the first effort succeeded, it is not a firewall issue.

I will continue monitoring the events and see if the issue clears again but does anyone have any ideas where I could begin researching?

Thanks,
Steve

https://social.technet.microsoft.com/Forums/getfile/1297512

My Server run OS Windows Server2012 DATACENTER on VMware

Detail MEMORY.DMP as below

------------------------------------------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
Machine Name:
Kernel base = 0xfffff800`a1217000 PsLoadedModuleList = 0xfffff800`a14f0250
Debug session time: Sat Jul 14 04:04:21.551 2018 (UTC + 0:00)
System Uptime: 237 days 20:14:54.479
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
................................
Loading unloaded module list
..............
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EF, {ffffe001636e5880, 0, 0, 0}

Probably caused by : wininit.exe

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffe001636e5880, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


PROCESS_OBJECT: ffffe001636e5880

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  WmiPrvSE.exe

BUGCHECK_STR:  0xEF_WmiPrvSE.exe

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800a1830d1c to fffff800a13679a0

STACK_TEXT:  
ffffd000`b70c69a8 fffff800`a1830d1c : 00000000`000000ef ffffe001`636e5880 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`b70c69b0 fffff800`a178fd50 : ffffe001`636e5880 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspCatchCriticalBreak+0xa4
ffffd000`b70c69f0 fffff800`a1673295 : 0000003c`7cef5401 00000000`00000000 ffffe001`636e5880 ffffe001`636e5880 : nt! ?? ::NNGAKEGL::`string'+0x4aba0
ffffd000`b70c6a50 fffff800`a1673022 : ffffffff`ffffffff ffffe001`63533080 ffffe001`636e5880 ffffe001`661f3880 : nt!PspTerminateProcess+0xe5
ffffd000`b70c6a90 fffff800`a13731b3 : ffffe001`636e5880 ffffe001`661f3880 ffffd000`b70c6b80 0000003c`7cef2cd0 : nt!NtTerminateProcess+0x9e
ffffd000`b70c6b00 00007ff8`35d20f0a : 00007ff8`32fc9fa9 00000000`00000000 0000003c`00000000 00000000`00000230 : nt!KiSystemServiceCopyEnd+0x13
0000003c`7d07da38 00007ff8`32fc9fa9 : 00000000`00000000 0000003c`00000000 00000000`00000230 00000000`00000000 : ntdll!NtTerminateProcess+0xa
0000003c`7d07da40 00007ff8`2773db9e : 00000000`00000000 00007ff8`276f8c60 0000003c`7d07daf0 00000000`00000230 : KERNELBASE!TerminateProcess+0x25
0000003c`7d07da70 00007ff8`2773959c : 00000000`00000001 0000003c`7cef5180 0000003c`00000170 00007ff8`27873430 : cimwin32!Process::ExecTerminate+0x12e
0000003c`7d07dae0 00007ff8`29399cb9 : 00007ff8`2770b7c0 0000003c`7cef3df0 00007ff8`27873430 0000003c`7c6ae200 : cimwin32!Process::ExecMethod+0x2dddc
0000003c`7d07db20 00007ff8`293999bc : 0000003c`7cef5450 0000003c`7cef5180 0000003c`7c65f200 00000000`00000000 : framedynos!Provider::ExecMethod+0xb5
0000003c`7d07dba0 00007ff6`5568d2a9 : 0000003c`7c6676a0 0000003c`7c636930 0000003c`7c636920 0000003c`7c650678 : framedynos!CWbemProviderGlue::ExecMethodAsync+0x40c
0000003c`7d07e1c0 00007ff6`5568ce4f : 00000000`00000000 00007ff8`00000000 0000003c`7d07e301 00000000`00000000 : wmiprvse!CInterceptor_IWbemSyncProvider::Helper_ExecMethodAsync+0x3a9
0000003c`7d07e280 00007ff8`338b2053 : 0000003c`00000000 0000003c`7c65b1c8 0000003c`7c672198 00000000`00000000 : wmiprvse!CInterceptor_IWbemSyncProvider::ExecMethodAsync+0x13f
0000003c`7d07e350 00007ff8`338bc70d : 0000003c`7d07e7f0 00007ff8`2a8f1b82 0000003c`7c652658 00007ff8`33c688a0 : RPCRT4!Invoke+0x73
0000003c`7d07e3d0 00007ff8`33c6d58a : 0000003c`7c652658 00007ff8`338ca501 0000003c`7c652658 00000000`00000000 : RPCRT4!NdrStubCall2+0x35e
0000003c`7d07ea40 00007ff8`2b04b746 : 00007ff8`00000001 00007ff8`2a8f13a0 0000003c`7c650a78 00000000`00000000 : combase!CStdStubBuffer_Invoke+0xa0 [d:\9147\com\combase\ndr\ndrole\stub.cxx @ 1582]
0000003c`7d07ea80 00007ff8`33c686ad : 00007ff8`2b04b700 0000003c`7d07ed50 00000000`00000000 00000000`00000000 : FastProx!CBaseStublet::Invoke+0x46
0000003c`7d07eab0 00007ff8`33af4f5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : combase!SyncStubInvoke+0x205 [d:\9147\com\combase\dcomrem\channelb.cxx @ 1664]
0000003c`7d07ec50 00007ff8`33c6951f : 00000000`00000010 0000003c`7c652870 0000003c`7d07ef20 00000000`00000000 : combase!CCtxComChnl::ContextInvoke+0x27a [d:\9147\com\combase\dcomrem\ctxchnl.cxx @ 1377]
0000003c`7d07ee60 00007ff8`33c68fb0 : 0000003c`7c652170 0000003c`7c652170 0000003c`7d07f390 00007ff8`33c68dc9 : combase!AppInvoke+0x1af [d:\9147\com\combase\dcomrem\channelb.cxx @ 1481]
0000003c`7d07ef50 00007ff8`33c69b35 : 00000000`00000000 00000000`00070005 0000003c`7c63f510 00007ff8`35cbd773 : combase!ComInvokeWithLockAndIPID+0x676 [d:\9147\com\combase\dcomrem\channelb.cxx @ 2314]
0000003c`7d07f190 00007ff8`338b23c7 : 00000000`00000000 00007ff8`33c69cf0 00000000`00000000 0000003c`7c61cf90 : combase!ThreadInvoke+0x48a [d:\9147\com\combase\dcomrem\channelb.cxx @ 5488]
0000003c`7d07f260 00007ff8`338b2220 : 0000003c`7c661550 00000000`00000000 0000003c`7d07f420 0000003c`7c4a0cc0 : RPCRT4!DispatchToStubInCNoAvrf+0x33
0000003c`7d07f2b0 00007ff8`338c9a78 : 0000003c`7c661550 00000000`00000000 0000003c`00000000 0000003c`7c652ec0 : RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x190
0000003c`7d07f3b0 00007ff8`338b2c86 : 00000005`092e6d51 0000003c`7c652ec0 00000000`00000000 0000003c`7c652ec0 : RPCRT4!LRPC_SCALL::DispatchRequest+0x4c9
0000003c`7d07f4c0 00007ff8`338b2ad8 : 00000039`00000000 0000003c`7c652c10 0000003c`7c652ec0 00000000`00000000 : RPCRT4!LRPC_SCALL::HandleRequest+0x291
0000003c`7d07f570 00007ff8`338b18bd : 0000003c`7c63de30 0000003c`7d07f700 00007ff8`3390edbc 0000003c`7c63df38 : RPCRT4!LRPC_SASSOCIATION::HandleRequest+0x238
0000003c`7d07f600 00007ff8`338b16be : 0000003c`7c61cb58 0000003c`7c63df38 00000000`00000000 00007ff8`3390edbc : RPCRT4!LRPC_ADDRESS::ProcessIO+0x444
0000003c`7d07f740 00007ff8`35cc58f0 : 0000003c`7c618d20 0000003c`7c61cb10 00007ff8`338b1600 0000003c`7d07f7f8 : RPCRT4!LrpcIoComplete+0x144
0000003c`7d07f7e0 00007ff8`35cc3c28 : 00000000`00000000 00007ff8`35cc5600 00000000`00000000 0000003c`7c644750 : ntdll!TppAlpcpExecuteCallback+0x210
0000003c`7d07f850 00007ff8`35b413d2 : 00000000`00000000 00007ff8`35cc33a0 0000003c`7c618d20 00000000`00000000 : ntdll!TppWorkerThread+0x888
0000003c`7d07fc30 00007ff8`35d003c4 : 00007ff8`35b413b0 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22
0000003c`7d07fc60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0xEF_WmiPrvSE.exe_IMAGE_wininit.exe

BUCKET_ID:  0xEF_WmiPrvSE.exe_IMAGE_wininit.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xef_wmiprvse.exe_image_wininit.exe

FAILURE_ID_HASH:  {dd961e7f-9fb2-75de-5c19-5602ba5ccdd2}

Followup: MachineOwner
---------

Hi,

I didn't set the server up from scratch someone else did, and now we have a few they may be due to him installing multiple versions of SQL server 5 which is not supported, but I am not sure. Here is a quick overview of the issues,

not expecting you do this all for me, but I spent the last 2-3 months since it's been installed trying to work through these issues, and am stuck.

1) when trying to remove some programs via Add/Remove programs I get you do not have the necessary permissions to remove this program. I also get this error sometimes when trying to run over admin tasks. 

2) Windows server essentials crashed and refused to run with a plugin issue. I have removed and reinstalled multiple times, and I get Windows server essentials needs to be configured before can be used, however, there is no option for config

3) Services not starting, no biggy for most, but one is the distributed com service

4) The password change notification target could not be contacted. We are getting 100s of these errors daily.

There are other issues as well, But I think these are the worst ones. I can provide more information on request. My prev server experience is 2000-2003 <g class="gr_ gr_21 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="21" id="21">so  been</g> a while.

Hi all,

i am uploading after effects template to my site, user came and upload his desired contents.

i update the template using scripting with user's contents and then render video so user get video with his uploaded text/images etc.

its working perfectly when i update a single template at a time but when multiple users come at the same time then they need multiple instances of after effects

so i open multiple instances of after effects by using "-m" with after effects shortcut

after looking at windows task manager there are both instances but the problem is

only once instance continue and the second one stop, after completion of first instance the second one still in pause status

i need 2,3 4 or whatever instances to work parallel without pause/stop

i am using windows server 2008 R2 with XAMP installed

We have a server (running Skyward) that was on 2008 R2 standard, and upgraded to 2012 R2 standard recently.  It is a virtual machine on Hyper-V, which has multiple other VMs running on the same servers which are just fine, which pretty much rules out hardware.  

Upon upgrading the OS, everything was fine until the first 137 windows updates were being applied - it either rebooted itself or BSOD but I didn't see a dmp file anywhere and in the system event log it said it was shut down improperly.  Server started acting wonky after being up and working for a few hours.  Most control panel items wouldn't load - instead explorer.exe would crash and not come back - I couldn't start task manager or start explorer from a run command line since windows+R didn't do anything either.  Rebooting was the only option (control alt del -> power icon in bottom right corner still works).  I couldn't get the windows updates control panel to work, nor could I get server manager to start.  I ended up reinstalling windows ontop of itself, which fixed most of those problems since sfc said everything was fine and dism just endlessly said it repaired the corruption but it never seemed to fix anything.  

After the second install of windows, windows updates showed 158 windows updates which was more than the first time I ran them... but I let it go and watched it closely to make sure it updated properly and it worked normally this time.  However, after being up for a few hours, explorer.exe will crash and even if I leave an elevated command prompt window open so I can relaunch explorer.exe, it still fails to launch and the only solution is to reboot it.  

Even though Explorer is crashing, the software on the server continues to work just fine (Skyward/IIS).  However, I obviously can't interact with it after explorer crashes.  Even after upgrading, DISM still reports it repaired the corruption, but there must be something else wrong.  I have NOT run any disk cleanup tools which I've seen in other posts that caused this type of problem.  

While running vssadmin list writers , I am getting the below delay which is causing backup failure. 

These may be delayed if a shadow copy is being prepared

Can someone please help me on this. 

Regards, suman

Hi, 

I have this  little  problem of  having a  black  screen  when I  log in to my  Windows  server 2012 R2.   Mysteriously  after  yesterday  I  cant  seem to  access  its  interface  already.   I can log on to the  Server  but  cant  see   the  GUI.    I g uess Explorer.exe   has  a  problem.   it  doesnt  respond  when i type  it on  RUN  command  BOX .  

Tried   Uninstalling the  GUI Feature  and  Reinstalling it  again  via  cmd line .  Same  result  still  cant  access  it.  has  anybody experience this and resolved  it  with out the need to  reinstall  the  Server.

Dear,

I have selected the following option in server, but then I got problem in client machine, to access it, by RDP. What to adjust, to resolve this?

Many Thanks & Best Regards, Hua Min

Recently we attempted to login to active directory and the log in to the domain from the windows 7 client took forever, when it finally logged in I received the error message on the machine...

( Windows could not connect to the system event notification service)

I ran the command net sh winsock reset, and rebooted the machine this did not work, I than stopped the service on the client machine and restarted the machine and this did not work either, I checked the logs on the server and I do not see anything that would cause this issue...

Thanks for your help

I've just taken over responsibility to maintain a Windows Server 2008 R2 that has been maintained by several different administrators.

While logged in as the Domain administrator, I click Windows Update and then Check for Updates, I receive a message saying Windows Update cannot currently check for updates, because updates on this computer are controlled by your system administrator.

When I'm logged in as the domain administrator, how do I correct this situation? It appears to be a permissions issue.

Thanks in advance for your help.

Is it possibel to disable admin$ share on a domain controller?  Is it possible to disable admin$ on an exchange server?  Is it possible to disable c$ and d$ drive administrative shares on a domain controller?  How about on an exchange server or member server?

I wold like to do this to lockdown security.

Dear,

Due to the following message (got when creating one user on the Win 2008 domain), does it mean the server domain has been corrupt?

How to resolve the problem that there were error captured (by Anti-virus application), exactly after the setup (from scratch) of Win 2008 R2 server with the relevant Domain?

Many Thanks & Best Regards, Hua Min

A client of ours recently upgraded servers from 2012 R2 to 2016 but is still running on a single label domain.  We were going to migrate to a full FQDN but the client decided to not do that just yet to save on time (I believe).  I also upgraded the forest and domain levels from 2003 to 2012 R2.  With the combination of the upgraded OS and greatly upgraded forest and domain levels, a few issues began to bubble to the surface.

First, we noticed issues with AD replication and saw that the network was still using FRS.  We migrated this to DFSR and resolved those issues.  Currently what we're seeing now is issues with DHCP.  DNS, obviously, is still configured with the single label (i.e. COMPANY).  DNS appears to be working as it did before the migration, at least in terms of resolving queries.  DHCP is currently set up with options 03 (router) and 06 (DNS servers).  Options 04 (time server) and 46 (NetBIOS over TCP/IP node type) were removed since they appeared to be superfluous.  

As DHCP leases expire, however, the client is stating that they cannot renew leases and must reboot the PC.  Once they do this, the PCs receive a new lease and continue working normally.  After reading many, many articles including Active Directory DNS Single Label Names (thank you, Ace), the issues appears to me to be clearly that the domain is still still single label and cannot properly function interact with DHCP and DNS.  The client, however, is arguing that this should have nothing to do with the problems they're seeing.

I'm hoping someone can give a more definitive answer since it's pretty clear that the technology, though it might have worked even through 2012 R2, simply is a throwback to NT4.  As a last fact, WINS was being used on the network prior to the migration to 2016 but was not migrated because it was believed to be too old and irrelevant.  If we're told that this must be re-implemented it will be.